<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="text/html; charset=UTF-8">
<style type="text/css" style="">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; font-family:Calibri,Arial,Helvetica,sans-serif">
<p>In July I added an accession record to ArchivesSpace and added instances to it. I looked at that accession record on several occasions after that.</p>
<p><br>
</p>
<p>Two weeks ago I looked at our ArchivesSpace accession records to gather statistics for our annual report and discovered that the accession record mentioned above no longer displayed in accessions browse view and was not returned as a search result when searched
for. The linked instances do still show up in search results, but the system says they are not linked to any other records.</p>
<p><br>
</p>
<p>If I try to add a new accession to the system with the same ID number it tells me it cannot add the record because that identifier is already in use. I have confirmed that the original accession is still listed in the accessions table in the backend database.</p>
<p><br>
</p>
<p>Does anyone have thoughts as to why this record was showing up in the staff interface but now is not? I have not run into this issue with any other records of any kind. The indexer appears to be working; changes we make- deletions and additions- are showing
up in the staff interface. </p>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> archivesspace_users_group-bounces@lyralists.lyrasis.org <archivesspace_users_group-bounces@lyralists.lyrasis.org> on behalf of archivesspace_users_group-request@lyralists.lyrasis.org
<archivesspace_users_group-request@lyralists.lyrasis.org><br>
<b>Sent:</b> Friday, October 6, 2017 8:20:04 AM<br>
<b>To:</b> archivesspace_users_group@lyralists.lyrasis.org<br>
<b>Subject:</b> Archivesspace_Users_Group Digest, Vol 51, Issue 2</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Send Archivesspace_Users_Group mailing list submissions to<br>
archivesspace_users_group@lyralists.lyrasis.org<br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group">
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a><br>
<br>
or, via email, send a message with subject or body 'help' to<br>
archivesspace_users_group-request@lyralists.lyrasis.org<br>
<br>
You can reach the person managing the list at<br>
archivesspace_users_group-owner@lyralists.lyrasis.org<br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Archivesspace_Users_Group digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: ArchivesSpace API - looking for working example of<br>
'Update a Resource' (Jason Loeffler)<br>
2. Re: ArchivesSpace API - looking for working example of<br>
'Update a Resource' (Seth Shaw)<br>
3. RFP for added container management functionality in<br>
ArchivesSpace (Christine Di Bella)<br>
4. Re: RFP for added container management functionality in<br>
ArchivesSpace (Detelich, Alicia)<br>
5. Linked Accessions on Agent Page Not Displaying (Harmeyer, Neal A)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Thu, 5 Oct 2017 14:14:04 -0400<br>
From: Jason Loeffler <j@minorscience.com><br>
To: Archivesspace Users Group<br>
<archivesspace_users_group@lyralists.lyrasis.org><br>
Subject: Re: [Archivesspace_Users_Group] ArchivesSpace API - looking<br>
for working example of 'Update a Resource'<br>
Message-ID:<br>
<CAP4gJsVCYWmom1cUHFFaJDfijT7GwRqwQbuQoMBq-QX-qaFwZg@mail.gmail.com><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Do you have an example of the update you'd like to make? Can you send an<br>
example of the code you're using to update the resource, as well as the<br>
error you're receiving?<br>
<br>
Best, Jason<br>
<br>
On Thu, Oct 5, 2017 at 2:11 PM, Suszczynski, Jeffrey <<br>
jsuszczynski@library.rochester.edu> wrote:<br>
<br>
> Hello, all ?<br>
><br>
><br>
><br>
> I?ve been working with the ArchivesSpace API for a while now, and can<br>
> successfully pull resource records out of a repository, etc. More<br>
> recently, though, I?ve been trying to update an existing resource within a<br>
> repository, and keep receiving errors.<br>
><br>
><br>
><br>
> Does anyone out there have a working code example of updating a resource<br>
> in ArchivesSpace, using a local file (preferably PHP, but Python or other<br>
> languages could be instructive as well)? I feel like I?m missing something<br>
> easy and obvious?<br>
><br>
><br>
><br>
> Thanks much in advance!<br>
> jeff<br>
><br>
><br>
><br>
><br>
><br>
> Jeff Suszczynski<br>
><br>
> Web Applications Programmer, River Campus Libraries<br>
><br>
> University of Rochester<br>
><br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Archivesspace_Users_Group mailing list<br>
> Archivesspace_Users_Group@lyralists.lyrasis.org<br>
> <a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group">
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a><br>
><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171005/d80c033a/attachment-0001.html">http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171005/d80c033a/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Thu, 5 Oct 2017 11:21:47 -0700<br>
From: Seth Shaw <seth.shaw@unlv.edu><br>
To: Archivesspace Users Group<br>
<archivesspace_users_group@lyralists.lyrasis.org><br>
Subject: Re: [Archivesspace_Users_Group] ArchivesSpace API - looking<br>
for working example of 'Update a Resource'<br>
Message-ID:<br>
<CANuEgP7VU-cmtOYqUfLinfG6gd33tEd9BOXc-6_qFWWdDo7+Jw@mail.gmail.com><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
See Noah Huffman's blog post on this topic (<br>
<a href="https://blogs.library.duke.edu/bitstreams/2016/09/21/archivesspace-api-fun/">https://blogs.library.duke.edu/bitstreams/2016/09/21/archivesspace-api-fun/</a>)<br>
and the associated scripts on github (<br>
<a href="https://github.com/duke-libraries/archivesspace-duke-scripts/tree/master/python">https://github.com/duke-libraries/archivesspace-duke-scripts/tree/master/python</a><br>
).<br>
<br>
Another example of updating a simple field (EAD ID) that I've written can<br>
be found at<br>
<a href="https://github.com/seth-shaw-unlv/small-stuff/blob/master/as-coll-mint/as_coll_mint.py">https://github.com/seth-shaw-unlv/small-stuff/blob/master/as-coll-mint/as_coll_mint.py</a><br>
<br>
<br>
On Thu, Oct 5, 2017 at 11:11 AM, Suszczynski, Jeffrey <<br>
jsuszczynski@library.rochester.edu> wrote:<br>
<br>
> Hello, all ?<br>
><br>
><br>
><br>
> I?ve been working with the ArchivesSpace API for a while now, and can<br>
> successfully pull resource records out of a repository, etc. More<br>
> recently, though, I?ve been trying to update an existing resource within a<br>
> repository, and keep receiving errors.<br>
><br>
><br>
><br>
> Does anyone out there have a working code example of updating a resource<br>
> in ArchivesSpace, using a local file (preferably PHP, but Python or other<br>
> languages could be instructive as well)? I feel like I?m missing something<br>
> easy and obvious?<br>
><br>
><br>
><br>
> Thanks much in advance!<br>
> jeff<br>
><br>
><br>
><br>
><br>
><br>
> Jeff Suszczynski<br>
><br>
> Web Applications Programmer, River Campus Libraries<br>
><br>
> University of Rochester<br>
><br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Archivesspace_Users_Group mailing list<br>
> Archivesspace_Users_Group@lyralists.lyrasis.org<br>
> <a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group">
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a><br>
><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171005/34774a2e/attachment-0001.html">http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171005/34774a2e/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Thu, 5 Oct 2017 18:40:23 +0000<br>
From: Christine Di Bella <christine.dibella@lyrasis.org><br>
To: Archivesspace Users Group<br>
<archivesspace_users_group@lyralists.lyrasis.org>, Archivesspace<br>
Member Reps <archivesspace_member_reps@lyralists.lyrasis.org>,<br>
"archivesspace_tac_uac@lyralists.lyrasis.org"<br>
<archivesspace_tac_uac@lyralists.lyrasis.org><br>
Cc: ArchivesSpace Board of Trustees mail list<br>
<archivesspace_bot_members@lyralists.lyrasis.org><br>
Subject: [Archivesspace_Users_Group] RFP for added container<br>
management functionality in ArchivesSpace<br>
Message-ID:<br>
<MWHPR08MB3456FB0664676FF6116F8399F1700@MWHPR08MB3456.namprd08.prod.outlook.com><br>
<br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
Hello ArchivesSpace members,<br>
<br>
ArchivesSpace is seeking proposals from individuals or firms interested in providing development for a limited scope project to add functionality to the container management area of the application. We are prioritizing this work for engagement of an outside
contractor based on expressed interest from a number of members, including one that may have funding to pay for it. Please feel free to forward this RFP on to people you think may be interested and qualified to do this work.<br>
<br>
We are asking that people please email proposals to me (christine.dibella@lyrasis.org<mailto:christine.dibella@lyrasis.org>) by October 27, 2017. Proposals should include a proposed action plan, pricing, timeline, names and contact information for at least
two client references, and examples of relevant work in ArchivesSpace or other applications. If people have questions about the RFP, feel free to send them my way as well. Laney can answer technical questions about the application and how delivery of code
would work.<br>
<br>
Issuing RFPs for specific projects is another strategy we are using to diversify our pool of available developers and continue to making substantial forward progress on the application. If you have any questions, or if you have suggestions for projects that
may be particularly appropriate for this type of treatment, please just let us know.<br>
<br>
Thanks,<br>
Christine<br>
<br>
Christine Di Bella<br>
ArchivesSpace Program Manager<br>
christine.dibella@lyrasis.org<mailto:christine.dibella@lyrasis.org><br>
800.999.8558 x2905<br>
678-235-2905<br>
cdibella13 (Skype)<br>
<br>
[ASpaceOrgHomeMedium]<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171005/6e170c80/attachment-0001.html">http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171005/6e170c80/attachment-0001.html</a>><br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: image002.jpg<br>
Type: image/jpeg<br>
Size: 6608 bytes<br>
Desc: image002.jpg<br>
URL: <<a href="http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171005/6e170c80/attachment-0001.jpg">http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171005/6e170c80/attachment-0001.jpg</a>><br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: ASpaceContainer Features RFP201710.pdf<br>
Type: application/pdf<br>
Size: 143039 bytes<br>
Desc: ASpaceContainer Features RFP201710.pdf<br>
URL: <<a href="http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171005/6e170c80/attachment-0001.pdf">http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171005/6e170c80/attachment-0001.pdf</a>><br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Thu, 5 Oct 2017 20:15:52 +0000<br>
From: "Detelich, Alicia" <alicia.detelich@yale.edu><br>
To: Archivesspace Users Group<br>
<archivesspace_users_group@lyralists.lyrasis.org><br>
Subject: Re: [Archivesspace_Users_Group] RFP for added container<br>
management functionality in ArchivesSpace<br>
Message-ID:<br>
<MWHPR08MB34856CD1F8717B521388FF318E700@MWHPR08MB3485.namprd08.prod.outlook.com><br>
<br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
Hi Christine,<br>
<br>
Thank you for sending this. It seems like an exciting project, and many of the listed features are much-needed. I wonder, though, about the advisability of adding the "ability to create top containers independent of specific material records" -
<a href="https://archivesspace.atlassian.net/browse/AR-1874">https://archivesspace.atlassian.net/browse/AR-1874</a>. You can already do this via the API - in fact, you have to create unlinked top containers before you can link them to material description records.
This is less than ideal, as it adds extra steps to the process - after creating the top containers, you then have to pull those top container URIs and link them to the material descriptions using a different endpoint.<br>
<br>
If the goal is to create top containers in bulk (and then link them to descriptions) via the staff interface, wouldn't it make more sense, as the JIRA ticket above notes, to add that ability within a material description record or RDE (<a href="https://archivesspace.atlassian.net/browse/AR-1873">https://archivesspace.atlassian.net/browse/AR-1873</a>),
rather than to enable the potential proliferation of unlinked containers? It seems like this could lead to all kinds of confusion and messy data in ArchivesSpace, especially if there are multiple unlinked containers with the same container profile, indicator,
etc. I think it might be better to solve the underlying issue rather than write a workaround into the application.<br>
<br>
Alicia<br>
<br>
---<br>
Alicia Detelich<br>
Archivist<br>
Manuscripts and Archives<br>
Yale University Libraries<br>
alicia.detelich@yale.edu<br>
<br>
From: archivesspace_users_group-bounces@lyralists.lyrasis.org [<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org</a>] On Behalf Of Christine Di Bella<br>
Sent: Thursday, October 5, 2017 2:40 PM<br>
To: Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org>; Archivesspace Member Reps <archivesspace_member_reps@lyralists.lyrasis.org>; archivesspace_tac_uac@lyralists.lyrasis.org<br>
Cc: ArchivesSpace Board of Trustees mail list <archivesspace_bot_members@lyralists.lyrasis.org><br>
Subject: [Archivesspace_Users_Group] RFP for added container management functionality in ArchivesSpace<br>
<br>
Hello ArchivesSpace members,<br>
<br>
ArchivesSpace is seeking proposals from individuals or firms interested in providing development for a limited scope project to add functionality to the container management area of the application. We are prioritizing this work for engagement of an outside
contractor based on expressed interest from a number of members, including one that may have funding to pay for it. Please feel free to forward this RFP on to people you think may be interested and qualified to do this work.<br>
<br>
We are asking that people please email proposals to me (christine.dibella@lyrasis.org<mailto:christine.dibella@lyrasis.org>) by October 27, 2017. Proposals should include a proposed action plan, pricing, timeline, names and contact information for at least
two client references, and examples of relevant work in ArchivesSpace or other applications. If people have questions about the RFP, feel free to send them my way as well. Laney can answer technical questions about the application and how delivery of code
would work.<br>
<br>
Issuing RFPs for specific projects is another strategy we are using to diversify our pool of available developers and continue to making substantial forward progress on the application. If you have any questions, or if you have suggestions for projects that
may be particularly appropriate for this type of treatment, please just let us know.<br>
<br>
Thanks,<br>
Christine<br>
<br>
Christine Di Bella<br>
ArchivesSpace Program Manager<br>
christine.dibella@lyrasis.org<mailto:christine.dibella@lyrasis.org><br>
800.999.8558 x2905<br>
678-235-2905<br>
cdibella13 (Skype)<br>
<br>
[ASpaceOrgHomeMedium]<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171005/ae009cec/attachment-0001.html">http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171005/ae009cec/attachment-0001.html</a>><br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: image002.jpg<br>
Type: image/jpeg<br>
Size: 4074 bytes<br>
Desc: image002.jpg<br>
URL: <<a href="http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171005/ae009cec/attachment-0001.jpg">http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171005/ae009cec/attachment-0001.jpg</a>><br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Fri, 6 Oct 2017 13:19:56 +0000<br>
From: "Harmeyer, Neal A" <harmeyna@purdue.edu><br>
To: Archivesspace Users Group<br>
<archivesspace_users_group@lyralists.lyrasis.org><br>
Subject: [Archivesspace_Users_Group] Linked Accessions on Agent Page<br>
Not Displaying<br>
Message-ID: <c6d394633290457292f656edf6a58be3@wppexc09.purdue.lcl><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
Hello everyone,<br>
<br>
It appears accessions that have a linked agent record are not displaying on the Agent's individual page in the public interface. All collections associated with the agents, whether as a source, subject, or creator, do display on the agent page as Related Collections
and/or Records-just not accessions. I have made certain the accessions in question are enabled for publication and discoverable in the public interface via search/browse, so it's not that the accessions are hidden from public view. I've highlighted an example
in the attached screenshots where an agent with 13 linked accessions/collections combined in the database gives the false impression there is only a single collection associated with that agent when landing on the agent page.<br>
<br>
Any chance I'm missing something? Or is there a reason accessions do not appear on an agent page? Purdue would like to see published accessions also appear on the page of an agent in the public interface.<br>
<br>
We're using version 2.1.2.<br>
<br>
Thank you,<br>
Neal<br>
--<br>
Neal Harmeyer<br>
Digital Archivist<br>
Archives and Special Collections<br>
Purdue University Libraries<br>
harmeyna@purdue.edu<<a href="mailto:harmeyna@purdue.edu">mailto:harmeyna@purdue.edu</a>><br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171006/70361b95/attachment.html">http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171006/70361b95/attachment.html</a>><br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: 2-accessions-display-agents-single-unprocessed-agent-linked.JPG<br>
Type: image/jpeg<br>
Size: 97442 bytes<br>
Desc: 2-accessions-display-agents-single-unprocessed-agent-linked.JPG<br>
URL: <<a href="http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171006/70361b95/attachment.jpe">http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171006/70361b95/attachment.jpe</a>><br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: 3-accessions-display-agents-name-page-related-materials.JPG<br>
Type: image/jpeg<br>
Size: 289215 bytes<br>
Desc: 3-accessions-display-agents-name-page-related-materials.JPG<br>
URL: <<a href="http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171006/70361b95/attachment-0001.jpe">http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171006/70361b95/attachment-0001.jpe</a>><br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: 1-accessions-display-agents-allresults.JPG<br>
Type: image/jpeg<br>
Size: 223113 bytes<br>
Desc: 1-accessions-display-agents-allresults.JPG<br>
URL: <<a href="http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171006/70361b95/attachment-0002.jpe">http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171006/70361b95/attachment-0002.jpe</a>><br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
Archivesspace_Users_Group mailing list<br>
Archivesspace_Users_Group@lyralists.lyrasis.org<br>
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a><br>
<br>
<br>
End of Archivesspace_Users_Group Digest, Vol 51, Issue 2<br>
********************************************************<br>
</div>
</span></font>
</body>
</html>