<div dir="ltr">Hi Greta,<div><br></div><div>There's a JIRA story <a href="https://archivesspace.atlassian.net/browse/AR-1002?filter=11600">here</a> that describes the issue. </div><div><br></div><div>It is in the backlog for our development partner, Hudson Molonglo. The fix will not appear in the next release. We'll work to get it addressed in a future release. Keep an eye on JIRA for activity on this issue. </div><div><br></div><div>Let me know if you have any questions. </div><div><br></div><div>Best, Jason</div><div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div dir="ltr"><div><div><font size="2" face="garamond, serif" style="background-color:rgb(255,255,255)" color="#666666">Jason Loeffler</font></div><div><font size="2" face="garamond, serif" style="background-color:rgb(255,255,255)" color="#666666">Technology Consultant | </font><span style="color:rgb(102,102,102);font-family:garamond,serif">The American Academy in Rome</span></div><div><font size="2" face="garamond, serif" style="background-color:rgb(255,255,255)" color="#666666">Minor Science | Application Development & Metadata Strategy</font></div><div><font size="2" face="garamond, serif" style="background-color:rgb(255,255,255)" color="#666666">Brooklyn, New York</font></div></div><div><font size="2" face="garamond, serif" style="background-color:rgb(255,255,255)" color="#666666"><a href="mailto:jason@minorscience.com" target="_blank">jason@minorscience.com</a></font></div><div><font size="2" face="garamond, serif" style="background-color:rgb(255,255,255)" color="#666666">(347) 405-0826</font></div><div><font size="2" face="garamond, serif" style="background-color:rgb(255,255,255)" color="#666666">minorscience (Skype)</font></div><div><br><br></div></div></div></div></div>
<br><div class="gmail_quote">On Fri, Dec 2, 2016 at 12:16 PM, Greta Kuriger Suiter <span dir="ltr"><<a href="mailto:gsuiter@mit.edu" target="_blank">gsuiter@mit.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Just wanted to record a problem with ASpace and see if anyone has a solution. When I try to add a sibling to a folder list it adds the sibling to the bottom of the list - not where I want it to go. I then have to drag the newly created folder up to where I wanted to put it. Anyone else have this problem / know a solution? When I do this I have the folder before the one I want to create highlighted, thinking that the added sibling would fall in after the highlighted one but that doesn't happen.<br>
<br>
Thanks for any help! I'll search this list history for answers too.<br>
-Greta<br>
<br>
Greta Kuriger Suiter<br>
Collections Archivist | Institute Archives & Special Collections<br>
MIT Libraries, Bldg. 14N-118 | 77 Massachusetts Ave., Cambridge, MA 02139-4307<br>
<a href="mailto:gsuiter@mit.edu">gsuiter@mit.edu</a><br>
My pronouns: she, her, hers<br>
<br>
<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-<wbr>bounces@lyralists.lyrasis.org</a> [mailto:<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_<wbr>group-bounces@lyralists.<wbr>lyrasis.org</a>] On Behalf Of <a href="mailto:archivesspace_users_group-request@lyralists.lyrasis.org">archivesspace_users_group-<wbr>request@lyralists.lyrasis.org</a><br>
Sent: Wednesday, November 16, 2016 9:40 AM<br>
To: <a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a><br>
Subject: Archivesspace_Users_Group Digest, Vol 40, Issue 2<br>
<br>
Send Archivesspace_Users_Group mailing list submissions to<br>
<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a><br>
<br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:archivesspace_users_group-request@lyralists.lyrasis.org">archivesspace_users_group-<wbr>request@lyralists.lyrasis.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:archivesspace_users_group-owner@lyralists.lyrasis.org">archivesspace_users_group-<wbr>owner@lyralists.lyrasis.org</a><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: LibraryHost (Tummino, Annie)<br>
2. Re: LibraryHost (Tummino, Annie)<br>
3. Check out the test site of the new ArchivesSpace PUI<br>
(Custer, Mark)<br>
4. Re: Check out the test site of the new ArchivesSpace PUI<br>
(Custer, Mark)<br>
5. new technical support option for ArchivesSpace members<br>
(Christine Di Bella)<br>
6. Job Posting: Digital Initiatives Librarian @ Brandeis<br>
University (Hong Jing)<br>
7. Job posting for Vanderbilt University (ArchivesSpaceHome)<br>
8. DACS 7.1.6 equivalent in ArchivesSpace (Cheri Crist)<br>
9. Problems working with archival object with large number of<br>
direct children (Sally Vermaaten)<br>
10. Re: [archivesspace] Problems working with archival object<br>
with large number of direct children (Runyon, Carolyn)<br>
11. Re: Problems working with archival object with large number<br>
of direct children (Ryan Edwards)<br>
12. Re: Problems working with archival object with large number<br>
of direct children (Jason Loeffler)<br>
13. Re: Problems working with archival object with large number<br>
of direct children (Jason Loeffler)<br>
14. Re: Problems working with archival object with large number<br>
of direct children (Joshua D. Shaw)<br>
15. Re: Problems working with archival object with large number<br>
of direct children (James Bullen)<br>
16. Re: Problems working with archival object with large number<br>
of direct children (Jason Loeffler)<br>
17. Re: Problems working with archival object with large number<br>
of direct children (James Bullen)<br>
18. A user who is set as manager of a collection can not create<br>
containers... (Gadsby, Eric T.)<br>
19. Re: Problems working with archival object with large number<br>
of direct children (Jason Loeffler)<br>
20. Re: Problems working with archival object with large number<br>
of direct children (James Bullen)<br>
21. Re: A user who is set as manager of a collection can not<br>
create containers... (Payten Giles)<br>
22. Re: A user who is set as manager of a collection can not<br>
create containers... (Payten Giles)<br>
23. Re: A user who is set as manager of a collection can not<br>
create containers... (Gadsby, Eric T.)<br>
24. Re: Problems working with archival object with large number<br>
of direct children (Joshua D. Shaw)<br>
25. Re: A user who is set as manager of a collection can not<br>
create containers... (Yvonne Kester)<br>
<br>
<br>
------------------------------<wbr>------------------------------<wbr>----------<br>
<br>
Message: 1<br>
Date: Thu, 10 Nov 2016 22:06:49 +0000<br>
From: "Tummino, Annie" <<a href="mailto:atummino@sunymaritime.edu">atummino@sunymaritime.edu</a>><br>
To: Archivesspace Users Group<br>
<<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a>><br>
Subject: Re: [Archivesspace_Users_Group] LibraryHost<br>
Message-ID: <<a href="mailto:d2478d3ae0184133ad042e3ec72119fe@EX02.sunymaritime.edu">d2478d3ae0184133ad042e3ec7211<wbr>9fe@EX02.sunymaritime.edu</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
P.S. I should add that this is really for creating resources (finding aids) and assumes you have already set up a repository and created an accession.<br>
<br>
From: <a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-<wbr>bounces@lyralists.lyrasis.org</a> [mailto:<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_<wbr>group-bounces@lyralists.<wbr>lyrasis.org</a>] On Behalf Of Clifford Allen<br>
Sent: Thursday, October 27, 2016 3:57 PM<br>
To: Archivesspace Users Group<br>
Subject: Re: [Archivesspace_Users_Group] LibraryHost<br>
<br>
Thanks Annie -- we're in the same boat. Good to know that the training is on hold; maybe that'll give us a little time to get more of our stuff together.<br>
<br>
I would be interested in seeing that user guide if it is not too much trouble. This is virgin territory for us though I have worked in porting out EAD to DAMs before... it's a little different.<br>
<br>
Cheers,<br>
Clifford<br>
<br>
On Thu, Oct 27, 2016 at 3:21 PM, Tummino, Annie <<a href="mailto:atummino@sunymaritime.edu">atummino@sunymaritime.edu</a><<wbr>mailto:<a href="mailto:atummino@sunymaritime.edu">atummino@sunymaritime.<wbr>edu</a>>> wrote:<br>
Hi Allen,<br>
We just started using LibraryHost a couple of months ago and it is working out great so far. I sent this same query to the SAA Lone Arrangers list and only got positive feedback about LibraryHost, which made me confident about moving forward. They also offer a free trial which is nice.<br>
<br>
Because we have no EAD files to begin with, we are starting with a relatively clean slate, so we didn?t need assistance with migration. Generally speaking, I am sure starting from scratch is a lot easier than what large institutions are confronting.<br>
<br>
I?ll note that the LibraryHost expert on ASpace is currently on maternity leave, so they are not able to do a training until she returns, but we are moving forward with branding in her absence. I have found that for our needs, I?ve been getting along just fine using the ASpace help center documentation, and it?s not really been a problem that we had to put off the training. We are creating a user guide which I?d be happy to share with you.<br>
<br>
Hope this helps,<br>
Annie<br>
<br>
From: <a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-<wbr>bounces@lyralists.lyrasis.org</a><<wbr>mailto:<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_<wbr>group-bounces@lyralists.<wbr>lyrasis.org</a>> [mailto:<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_<wbr>group-bounces@lyralists.<wbr>lyrasis.org</a><mailto:<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspa<wbr>ce_users_group-bounces@<wbr>lyralists.lyrasis.org</a>>] On Behalf Of Clifford Allen<br>
Sent: Thursday, October 27, 2016 11:27 AM<br>
To: <a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a><mailto:<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">a<wbr>rchivesspace_users_group@<wbr>lyralists.lyrasis.org</a>><br>
Subject: [Archivesspace_Users_Group] LibraryHost<br>
<br>
Hi All,<br>
<br>
Forgive me if this has been brought up before and is a dead-horse topic, but as someone who is just beginning to implement ArchivesSpace, what are the advantages/disadvantages of LibraryHost as compared to Atlas and LYRASIS? As we are a small institution their lower price points are attractive, but I'm wondering if that is because certain necessary services/aspects aren't being offered.<br>
<br>
Thanks so much in advance for weighing in.<br>
<br>
Sincerely,<br>
<br>
--<br>
Clifford Allen<br>
Archivist | The Watermill Center | Robert Wilson<br>
115 W 29th St., 10th Fl., New York, NY 10001<br>
main: <a href="tel:%2B1%20212%20253%207484%20x%20113" value="+12122537484">+1 212 253 7484 x 113</a><tel:%2B1%20212%20253%207484%<wbr>20x%20113><br>
<a href="mailto:clifford.allen@watermillcenter.org">clifford.allen@<wbr>watermillcenter.org</a><mailto:<a href="mailto:clifford.allen@watermillcenter.org">cli<wbr>fford.allen@watermillcenter.<wbr>org</a>> | <a href="http://www.watermillcenter.org" rel="noreferrer" target="_blank">www.watermillcenter.org</a><<a href="http://www.watermillcenter.org" rel="noreferrer" target="_blank">http:/<wbr>/www.watermillcenter.org</a>><br>
<br>
JOIN US! | BECOME A MEMBER OF THE WATERMILL CENTER TODAY<br>
<br>
Connect with us on Facebook<<a href="https://www.facebook.com/thewatermillcenter" rel="noreferrer" target="_blank">https://www.facebook.<wbr>com/thewatermillcenter</a>>, Twitter<<a href="http://twitter.com/#%21/watermillcenter" rel="noreferrer" target="_blank">http://twitter.com/#%<wbr>21/watermillcenter</a>>, Instagram<<a href="http://instagram.com/watermillcenter" rel="noreferrer" target="_blank">http://instagram.<wbr>com/watermillcenter</a>>, Flickr,<<a href="http://www.flickr.com/photos/watermillresidencies/" rel="noreferrer" target="_blank">http://www.flickr.com/<wbr>photos/watermillresidencies/</a>> and Vimeo<<a href="https://vimeo.com/watermillcenter" rel="noreferrer" target="_blank">https://vimeo.com/<wbr>watermillcenter</a>>. Join our email list!<<a href="http://watermillcenter.org/content/newsletter-signup" rel="noreferrer" target="_blank">http://watermillcenter.<wbr>org/content/newsletter-signup</a>><br>
<br>
The Watermill Center is the principal operation of the Byrd Hoffman Watermill Foundation, a US 501(c)3 organization incorporated in the state of New York.<br>
<br>
______________________________<wbr>_________________<br>
Archivesspace_Users_Group mailing list<br>
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a><mailto:<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">A<wbr>rchivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a>><br>
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a><br>
<br>
<br>
<br>
--<br>
Clifford Allen<br>
Archivist | The Watermill Center | Robert Wilson<br>
115 W 29th St., 10th Fl., New York, NY 10001<br>
main: <a href="tel:%2B1%20212%20253%207484%20x%20113" value="+12122537484">+1 212 253 7484 x 113</a><br>
<a href="mailto:clifford.allen@watermillcenter.org">clifford.allen@<wbr>watermillcenter.org</a><mailto:<a href="mailto:clifford.allen@watermillcenter.org">cli<wbr>fford.allen@watermillcenter.<wbr>org</a>> | <a href="http://www.watermillcenter.org" rel="noreferrer" target="_blank">www.watermillcenter.org</a><<a href="http://www.watermillcenter.org" rel="noreferrer" target="_blank">http:/<wbr>/www.watermillcenter.org</a>><br>
<br>
JOIN US! | BECOME A MEMBER OF THE WATERMILL CENTER TODAY<br>
<br>
Connect with us on Facebook<<a href="https://www.facebook.com/thewatermillcenter" rel="noreferrer" target="_blank">https://www.facebook.<wbr>com/thewatermillcenter</a>>, Twitter<<a href="http://twitter.com/#%21/watermillcenter" rel="noreferrer" target="_blank">http://twitter.com/#%<wbr>21/watermillcenter</a>>, Instagram<<a href="http://instagram.com/watermillcenter" rel="noreferrer" target="_blank">http://instagram.<wbr>com/watermillcenter</a>>, Flickr,<<a href="http://www.flickr.com/photos/watermillresidencies/" rel="noreferrer" target="_blank">http://www.flickr.com/<wbr>photos/watermillresidencies/</a>> and Vimeo<<a href="https://vimeo.com/watermillcenter" rel="noreferrer" target="_blank">https://vimeo.com/<wbr>watermillcenter</a>>. Join our email list!<<a href="http://watermillcenter.org/content/newsletter-signup" rel="noreferrer" target="_blank">http://watermillcenter.<wbr>org/content/newsletter-signup</a>><br>
<br>
The Watermill Center is the principal operation of the Byrd Hoffman Watermill Foundation, a US 501(c)3 organization incorporated in the state of New York.<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20161110/2b464b8f/attachment-0001.html" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>pipermail/archivesspace_users_<wbr>group/attachments/20161110/<wbr>2b464b8f/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Thu, 10 Nov 2016 22:08:25 +0000<br>
From: "Tummino, Annie" <<a href="mailto:atummino@sunymaritime.edu">atummino@sunymaritime.edu</a>><br>
To: Archivesspace Users Group<br>
<<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a>><br>
Subject: Re: [Archivesspace_Users_Group] LibraryHost<br>
Message-ID: <<a href="mailto:523f6c8459934b039830b01928647d8c@EX02.sunymaritime.edu">523f6c8459934b039830b01928647<wbr>d8c@EX02.sunymaritime.edu</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Sorry folks! I was trying to send this to Clifford and mistakenly sent to the whole list. Well, if anyone else wants to see our Guide, there you have it. That?s what happens when you try to do things at the end of the day when you are about to leave.<br>
Best,<br>
Annie<br>
<br>
From: <a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-<wbr>bounces@lyralists.lyrasis.org</a> [mailto:<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_<wbr>group-bounces@lyralists.<wbr>lyrasis.org</a>] On Behalf Of Tummino, Annie<br>
Sent: Thursday, November 10, 2016 5:07 PM<br>
To: Archivesspace Users Group<br>
Subject: Re: [Archivesspace_Users_Group] LibraryHost<br>
<br>
P.S. I should add that this is really for creating resources (finding aids) and assumes you have already set up a repository and created an accession.<br>
<br>
From: <a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-<wbr>bounces@lyralists.lyrasis.org</a><<wbr>mailto:<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_<wbr>group-bounces@lyralists.<wbr>lyrasis.org</a>> [mailto:<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_<wbr>group-bounces@lyralists.<wbr>lyrasis.org</a>] On Behalf Of Clifford Allen<br>
Sent: Thursday, October 27, 2016 3:57 PM<br>
To: Archivesspace Users Group<br>
Subject: Re: [Archivesspace_Users_Group] LibraryHost<br>
<br>
Thanks Annie -- we're in the same boat. Good to know that the training is on hold; maybe that'll give us a little time to get more of our stuff together.<br>
<br>
I would be interested in seeing that user guide if it is not too much trouble. This is virgin territory for us though I have worked in porting out EAD to DAMs before... it's a little different.<br>
<br>
Cheers,<br>
Clifford<br>
<br>
On Thu, Oct 27, 2016 at 3:21 PM, Tummino, Annie <<a href="mailto:atummino@sunymaritime.edu">atummino@sunymaritime.edu</a><<wbr>mailto:<a href="mailto:atummino@sunymaritime.edu">atummino@sunymaritime.<wbr>edu</a>>> wrote:<br>
Hi Allen,<br>
We just started using LibraryHost a couple of months ago and it is working out great so far. I sent this same query to the SAA Lone Arrangers list and only got positive feedback about LibraryHost, which made me confident about moving forward. They also offer a free trial which is nice.<br>
<br>
Because we have no EAD files to begin with, we are starting with a relatively clean slate, so we didn?t need assistance with migration. Generally speaking, I am sure starting from scratch is a lot easier than what large institutions are confronting.<br>
<br>
I?ll note that the LibraryHost expert on ASpace is currently on maternity leave, so they are not able to do a training until she returns, but we are moving forward with branding in her absence. I have found that for our needs, I?ve been getting along just fine using the ASpace help center documentation, and it?s not really been a problem that we had to put off the training. We are creating a user guide which I?d be happy to share with you.<br>
<br>
Hope this helps,<br>
Annie<br>
<br>
From: <a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-<wbr>bounces@lyralists.lyrasis.org</a><<wbr>mailto:<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_<wbr>group-bounces@lyralists.<wbr>lyrasis.org</a>> [mailto:<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_<wbr>group-bounces@lyralists.<wbr>lyrasis.org</a><mailto:<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspa<wbr>ce_users_group-bounces@<wbr>lyralists.lyrasis.org</a>>] On Behalf Of Clifford Allen<br>
Sent: Thursday, October 27, 2016 11:27 AM<br>
To: <a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a><mailto:<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">a<wbr>rchivesspace_users_group@<wbr>lyralists.lyrasis.org</a>><br>
Subject: [Archivesspace_Users_Group] LibraryHost<br>
<br>
Hi All,<br>
<br>
Forgive me if this has been brought up before and is a dead-horse topic, but as someone who is just beginning to implement ArchivesSpace, what are the advantages/disadvantages of LibraryHost as compared to Atlas and LYRASIS? As we are a small institution their lower price points are attractive, but I'm wondering if that is because certain necessary services/aspects aren't being offered.<br>
<br>
Thanks so much in advance for weighing in.<br>
<br>
Sincerely,<br>
<br>
--<br>
Clifford Allen<br>
Archivist | The Watermill Center | Robert Wilson<br>
115 W 29th St., 10th Fl., New York, NY 10001<br>
main: <a href="tel:%2B1%20212%20253%207484%20x%20113" value="+12122537484">+1 212 253 7484 x 113</a><tel:%2B1%20212%20253%207484%<wbr>20x%20113><br>
<a href="mailto:clifford.allen@watermillcenter.org">clifford.allen@<wbr>watermillcenter.org</a><mailto:<a href="mailto:clifford.allen@watermillcenter.org">cli<wbr>fford.allen@watermillcenter.<wbr>org</a>> | <a href="http://www.watermillcenter.org" rel="noreferrer" target="_blank">www.watermillcenter.org</a><<a href="http://www.watermillcenter.org" rel="noreferrer" target="_blank">http:/<wbr>/www.watermillcenter.org</a>><br>
<br>
JOIN US! | BECOME A MEMBER OF THE WATERMILL CENTER TODAY<br>
<br>
Connect with us on Facebook<<a href="https://www.facebook.com/thewatermillcenter" rel="noreferrer" target="_blank">https://www.facebook.<wbr>com/thewatermillcenter</a>>, Twitter<<a href="http://twitter.com/#%21/watermillcenter" rel="noreferrer" target="_blank">http://twitter.com/#%<wbr>21/watermillcenter</a>>, Instagram<<a href="http://instagram.com/watermillcenter" rel="noreferrer" target="_blank">http://instagram.<wbr>com/watermillcenter</a>>, Flickr,<<a href="http://www.flickr.com/photos/watermillresidencies/" rel="noreferrer" target="_blank">http://www.flickr.com/<wbr>photos/watermillresidencies/</a>> and Vimeo<<a href="https://vimeo.com/watermillcenter" rel="noreferrer" target="_blank">https://vimeo.com/<wbr>watermillcenter</a>>. Join our email list!<<a href="http://watermillcenter.org/content/newsletter-signup" rel="noreferrer" target="_blank">http://watermillcenter.<wbr>org/content/newsletter-signup</a>><br>
<br>
The Watermill Center is the principal operation of the Byrd Hoffman Watermill Foundation, a US 501(c)3 organization incorporated in the state of New York.<br>
<br>
______________________________<wbr>_________________<br>
Archivesspace_Users_Group mailing list<br>
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a><mailto:<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">A<wbr>rchivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a>><br>
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a><br>
<br>
<br>
<br>
--<br>
Clifford Allen<br>
Archivist | The Watermill Center | Robert Wilson<br>
115 W 29th St., 10th Fl., New York, NY 10001<br>
main: <a href="tel:%2B1%20212%20253%207484%20x%20113" value="+12122537484">+1 212 253 7484 x 113</a><br>
<a href="mailto:clifford.allen@watermillcenter.org">clifford.allen@<wbr>watermillcenter.org</a><mailto:<a href="mailto:clifford.allen@watermillcenter.org">cli<wbr>fford.allen@watermillcenter.<wbr>org</a>> | <a href="http://www.watermillcenter.org" rel="noreferrer" target="_blank">www.watermillcenter.org</a><<a href="http://www.watermillcenter.org" rel="noreferrer" target="_blank">http:/<wbr>/www.watermillcenter.org</a>><br>
<br>
JOIN US! | BECOME A MEMBER OF THE WATERMILL CENTER TODAY<br>
<br>
Connect with us on Facebook<<a href="https://www.facebook.com/thewatermillcenter" rel="noreferrer" target="_blank">https://www.facebook.<wbr>com/thewatermillcenter</a>>, Twitter<<a href="http://twitter.com/#%21/watermillcenter" rel="noreferrer" target="_blank">http://twitter.com/#%<wbr>21/watermillcenter</a>>, Instagram<<a href="http://instagram.com/watermillcenter" rel="noreferrer" target="_blank">http://instagram.<wbr>com/watermillcenter</a>>, Flickr,<<a href="http://www.flickr.com/photos/watermillresidencies/" rel="noreferrer" target="_blank">http://www.flickr.com/<wbr>photos/watermillresidencies/</a>> and Vimeo<<a href="https://vimeo.com/watermillcenter" rel="noreferrer" target="_blank">https://vimeo.com/<wbr>watermillcenter</a>>. Join our email list!<<a href="http://watermillcenter.org/content/newsletter-signup" rel="noreferrer" target="_blank">http://watermillcenter.<wbr>org/content/newsletter-signup</a>><br>
<br>
The Watermill Center is the principal operation of the Byrd Hoffman Watermill Foundation, a US 501(c)3 organization incorporated in the state of New York.<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20161110/9fa832cd/attachment-0001.html" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>pipermail/archivesspace_users_<wbr>group/attachments/20161110/<wbr>9fa832cd/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Fri, 11 Nov 2016 14:47:59 +0000<br>
From: "Custer, Mark" <<a href="mailto:mark.custer@yale.edu">mark.custer@yale.edu</a>><br>
To: "Archivesspace Users Group<br>
(<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a>)"<br>
<<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a>><br>
Subject: [Archivesspace_Users_Group] Check out the test site of the<br>
new ArchivesSpace PUI<br>
Message-ID:<br>
<<a href="mailto:BN3PR08MB131830F17AA189BFAE17674E8CBB0@BN3PR08MB1318.namprd08.prod.outlook.com">BN3PR08MB131830F17AA189BFAE17<wbr>674E8CBB0@BN3PR08MB1318.<wbr>namprd08.prod.outlook.com</a>><br>
<br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
Dear ArchivesSpace colleagues:<br>
<br>
I am writing to provide an update about the development of the new ArchivesSpace Public Interface. As a reminder, here is the release timeline that we drafted and shared earlier in the year:<br>
<br>
<br>
* candidate release, 12/16/2016<br>
<br>
* official testing period, 12/19/2016 - 2/28/2017<br>
<br>
* official release, 3/31/2017<br>
<br>
We're still on track to have everything done in time for an official release in March, but it's likely that we will push that candidate release date back a few weeks. Since we haven't changed the date yet I don't have a new date to share at this time, but if we do push the date back it will probably be postponed to January.<br>
<br>
In the meantime, I also wanted to share a link with everyone to a working version of the new public interface so that you could see things in action before everything is finished. You can access that website here:<br>
<br>
<a href="http://pui.hudmol.com/" rel="noreferrer" target="_blank">http://pui.hudmol.com/</a><br>
(and thanks to Hudson Molonglo for hosting this site for us during the development process!!!)<br>
<br>
Please note that this site is still a work in progress. You might stumble across bugs, and it's possible that some features could stop working from one day to the next. Also, not all features have been added (e.g. "Record Group" / Classification pages) or fully implemented yet (e.g. the "Collection organization" navigation sidebar). In any event, this site will provide a more interactive way to explore the development process before the design has been finished. In the coming weeks, we will also create a few introductory videos for the new PUI that will focus on and explain a few of the new, exciting features.<br>
<br>
You can also follow along with the development process at the ArchivesSpace PUI wiki: <a href="https://archivesspace.atlassian.net/wiki/display/ADC/Public+Interface+Enhancement+Project" rel="noreferrer" target="_blank">https://archivesspace.<wbr>atlassian.net/wiki/display/<wbr>ADC/Public+Interface+<wbr>Enhancement+Project</a><<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_wiki_display_ADC_Public-26-2343-3BInterface-26-2343-3BEnhancement-26-2343-3BProject&d=CwMFAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=s7ciGQfUJeaV_ryx908hbeXDoU9aqDwDN0Z0VbfsJ3Y&m=EVhE7hGgEiFUwEqMCd6wOUjBAjB-m9qD3KnMCwCnzGk&s=9J-sJPfocPm1WF4QSm9MvnLFX4jAWKWwRSNMGBqB5jc&e=" rel="noreferrer" target="_blank">https://<wbr>urldefense.proofpoint.com/v2/<wbr>url?u=https-3A__archivesspace.<wbr>atlassian.net_wiki_display_<wbr>ADC_Public-26-2343-<wbr>3BInterface-26-2343-<wbr>3BEnhancement-26-2343-<wbr>3BProject&d=CwMFAg&c=-<wbr>dg2m7zWuuDZ0MUcV7Sdqw&r=<wbr>s7ciGQfUJeaV_<wbr>ryx908hbeXDoU9aqDwDN0Z0VbfsJ3Y<wbr>&m=<wbr>EVhE7hGgEiFUwEqMCd6wOUjBAjB-<wbr>m9qD3KnMCwCnzGk&s=9J-<wbr>sJPfocPm1WF4QSm9MvnLFX4jAWKWwR<wbr>SNMGBqB5jc&e=</a>><br>
<br>
More news soon,<br>
<br>
Mark Custer<br>
On behalf of the ArchivesSpace Public Interface development group.<br>
<br>
* James Bullen, Hudson Molonglo<br>
<br>
* Mark Cooper, LYRASIS<br>
<br>
* Mark Custer, Yale University<br>
<br>
* Bobbi Fox, Harvard University<br>
<br>
* Payten Giles, Hudson Molonglo<br>
<br>
* Brian Hoffman, Consultant<br>
<br>
* Susan Pyzynski, Harvard University<br>
<br>
* Mark Triggs, Hudson Molonglo<br>
<br>
* Brad Westbrook, ArchivesSpace<br>
<br>
* Melissa Wisner, Yale University<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20161111/b1ef5532/attachment-0001.html" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>pipermail/archivesspace_users_<wbr>group/attachments/20161111/<wbr>b1ef5532/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Fri, 11 Nov 2016 15:18:52 +0000<br>
From: "Custer, Mark" <<a href="mailto:mark.custer@yale.edu">mark.custer@yale.edu</a>><br>
To: Archivesspace Users Group<br>
<<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a>><br>
Subject: Re: [Archivesspace_Users_Group] Check out the test site of<br>
the new ArchivesSpace PUI<br>
Message-ID:<br>
<<a href="mailto:BN3PR08MB1318741EC76BD5401A2DBC918CBB0@BN3PR08MB1318.namprd08.prod.outlook.com">BN3PR08MB1318741EC76BD5401A2D<wbr>BC918CBB0@BN3PR08MB1318.<wbr>namprd08.prod.outlook.com</a>><br>
<br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
All,<br>
<br>
I regret that I didn't include at least one search example with the previous announcement. Since today's the first day of the 2016 World Chess Championship, here's a timely one:<br>
<br>
<a href="http://pui.hudmol.com/search?utf8=%E2%9C%93&q=chess" rel="noreferrer" target="_blank">http://pui.hudmol.com/search?<wbr>utf8=%E2%9C%93&q=chess</a><br>
<br>
I'll also come back to this example later on in one of the introductory videos, since I think it might be a good case to explain how the new archival inheritance feature will work once it's implemented (see <a href="https://archivesspace.atlassian.net/browse/AR-1300" rel="noreferrer" target="_blank">https://archivesspace.<wbr>atlassian.net/browse/AR-1300</a>).<br>
<br>
All my best,<br>
<br>
Mark<br>
<br>
From: <a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-<wbr>bounces@lyralists.lyrasis.org</a> [mailto:<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_<wbr>group-bounces@lyralists.<wbr>lyrasis.org</a>] On Behalf Of Custer, Mark<br>
Sent: Friday, 11 November, 2016 9:48 AM<br>
To: Archivesspace Users Group (<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a>)<br>
Subject: [Archivesspace_Users_Group] Check out the test site of the new ArchivesSpace PUI<br>
<br>
Dear ArchivesSpace colleagues:<br>
<br>
I am writing to provide an update about the development of the new ArchivesSpace Public Interface. As a reminder, here is the release timeline that we drafted and shared earlier in the year:<br>
<br>
<br>
* candidate release, 12/16/2016<br>
<br>
* official testing period, 12/19/2016 - 2/28/2017<br>
<br>
* official release, 3/31/2017<br>
<br>
We're still on track to have everything done in time for an official release in March, but it's likely that we will push that candidate release date back a few weeks. Since we haven't changed the date yet I don't have a new date to share at this time, but if we do push the date back it will probably be postponed to January.<br>
<br>
In the meantime, I also wanted to share a link with everyone to a working version of the new public interface so that you could see things in action before everything is finished. You can access that website here:<br>
<br>
<a href="http://pui.hudmol.com/" rel="noreferrer" target="_blank">http://pui.hudmol.com/</a><<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__pui.hudmol.com_&d=CwMFAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=s7ciGQfUJeaV_ryx908hbeXDoU9aqDwDN0Z0VbfsJ3Y&m=mHKsaKwdKo1giNBjiurqEHO18veSK4gHeKMYhEh3Y_s&s=cT2ROAsYvRYwVtJMlVbfF0Uij0OilGhnxk88YuxsoKM&e=" rel="noreferrer" target="_blank">https:/<wbr>/urldefense.proofpoint.com/v2/<wbr>url?u=http-3A__pui.hudmol.com_<wbr>&d=CwMFAg&c=-<wbr>dg2m7zWuuDZ0MUcV7Sdqw&r=<wbr>s7ciGQfUJeaV_<wbr>ryx908hbeXDoU9aqDwDN0Z0VbfsJ3Y<wbr>&m=<wbr>mHKsaKwdKo1giNBjiurqEHO18veSK4<wbr>gHeKMYhEh3Y_s&s=<wbr>cT2ROAsYvRYwVtJMlVbfF0Uij0OilG<wbr>hnxk88YuxsoKM&e=</a>><br>
(and thanks to Hudson Molonglo for hosting this site for us during the development process!!!)<br>
<br>
Please note that this site is still a work in progress. You might stumble across bugs, and it's possible that some features could stop working from one day to the next. Also, not all features have been added (e.g. "Record Group" / Classification pages) or fully implemented yet (e.g. the "Collection organization" navigation sidebar). In any event, this site will provide a more interactive way to explore the development process before the design has been finished. In the coming weeks, we will also create a few introductory videos for the new PUI that will focus on and explain a few of the new, exciting features.<br>
<br>
You can also follow along with the development process at the ArchivesSpace PUI wiki: <a href="https://archivesspace.atlassian.net/wiki/display/ADC/Public+Interface+Enhancement+Project" rel="noreferrer" target="_blank">https://archivesspace.<wbr>atlassian.net/wiki/display/<wbr>ADC/Public+Interface+<wbr>Enhancement+Project</a><<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_wiki_display_ADC_Public-26-2343-3BInterface-26-2343-3BEnhancement-26-2343-3BProject&d=CwMFAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=s7ciGQfUJeaV_ryx908hbeXDoU9aqDwDN0Z0VbfsJ3Y&m=EVhE7hGgEiFUwEqMCd6wOUjBAjB-m9qD3KnMCwCnzGk&s=9J-sJPfocPm1WF4QSm9MvnLFX4jAWKWwRSNMGBqB5jc&e=" rel="noreferrer" target="_blank">https://<wbr>urldefense.proofpoint.com/v2/<wbr>url?u=https-3A__archivesspace.<wbr>atlassian.net_wiki_display_<wbr>ADC_Public-26-2343-<wbr>3BInterface-26-2343-<wbr>3BEnhancement-26-2343-<wbr>3BProject&d=CwMFAg&c=-<wbr>dg2m7zWuuDZ0MUcV7Sdqw&r=<wbr>s7ciGQfUJeaV_<wbr>ryx908hbeXDoU9aqDwDN0Z0VbfsJ3Y<wbr>&m=<wbr>EVhE7hGgEiFUwEqMCd6wOUjBAjB-<wbr>m9qD3KnMCwCnzGk&s=9J-<wbr>sJPfocPm1WF4QSm9MvnLFX4jAWKWwR<wbr>SNMGBqB5jc&e=</a>><br>
<br>
More news soon,<br>
<br>
Mark Custer<br>
On behalf of the ArchivesSpace Public Interface development group.<br>
<br>
* James Bullen, Hudson Molonglo<br>
<br>
* Mark Cooper, LYRASIS<br>
<br>
* Mark Custer, Yale University<br>
<br>
* Bobbi Fox, Harvard University<br>
<br>
* Payten Giles, Hudson Molonglo<br>
<br>
* Brian Hoffman, Consultant<br>
<br>
* Susan Pyzynski, Harvard University<br>
<br>
* Mark Triggs, Hudson Molonglo<br>
<br>
* Brad Westbrook, ArchivesSpace<br>
<br>
* Melissa Wisner, Yale University<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20161111/5b70d59c/attachment-0001.html" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>pipermail/archivesspace_users_<wbr>group/attachments/20161111/<wbr>5b70d59c/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Mon, 14 Nov 2016 14:19:02 +0000<br>
From: Christine Di Bella <<a href="mailto:christine.dibella@lyrasis.org">christine.dibella@lyrasis.org</a><wbr>><br>
To: Archivesspace Users Group<br>
<<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a>>, Archivesspace<br>
Member Reps <<a href="mailto:archivesspace_member_reps@lyralists.lyrasis.org">archivesspace_member_reps@<wbr>lyralists.lyrasis.org</a>>,<br>
"<a href="mailto:archivesspace_tac_uac@lyralists.lyrasis.org">archivesspace_tac_uac@<wbr>lyralists.lyrasis.org</a>"<br>
<<a href="mailto:archivesspace_tac_uac@lyralists.lyrasis.org">archivesspace_tac_uac@<wbr>lyralists.lyrasis.org</a>><br>
Cc: "<a href="mailto:archivesspace_bot_members@lyralists.lyrasis.org">archivesspace_bot_members@<wbr>lyralists.lyrasis.org</a>"<br>
<<a href="mailto:archivesspace_bot_members@lyralists.lyrasis.org">archivesspace_bot_members@<wbr>lyralists.lyrasis.org</a>><br>
Subject: [Archivesspace_Users_Group] new technical support option for<br>
ArchivesSpace members<br>
Message-ID:<br>
<<a href="mailto:DM2PR0801MB08486FEAD74E619903115941F1BC0@DM2PR0801MB0848.namprd08.prod.outlook.com">DM2PR0801MB08486FEAD74E619903<wbr>115941F1BC0@DM2PR0801MB0848.<wbr>namprd08.prod.outlook.com</a>><br>
<br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
Dear ArchivesSpace members,<br>
<br>
ArchivesSpace is happy to announce an additional way for ArchivesSpace members to receive technical support. Courtesy of resources approved by the ArchivesSpace Governance Board, staff from LYRASIS Technology Services will be taking an added role in providing help to individual ArchivesSpace members and contributing to the technical documentation for the application.<br>
<br>
As befits a Community-Supported Software application, when you need help, we encourage you to look to the community first by posting to the Users Group listserv. Given the breadth of knowledge and experience on the listserv, and the sheer number of people participating (currently over 850 subscribers), many issues will be resolved quickly this way and everyone will benefit from the discussion of the issue and its solution.<br>
<br>
If you are unable to resolve the issue using the listserv, or if you think you need more individualized assistance from the start, please email <a href="mailto:ArchivesSpaceHome@lyrasis.org">ArchivesSpaceHome@lyrasis.org</a><<wbr>mailto:<a href="mailto:ArchivesSpaceHome@lyrasis.org">ArchivesSpaceHome@<wbr>lyrasis.org</a>> with your issue. If it requires technical assistance beyond the program staff's expertise, a program staff member will create a ticket and LYRASIS Technology Services staff will follow up with you. When applicable, once the issue has been resolved, LYRASIS Technology Services staff will also update related technical documentation on GitHub to make the issue easier to resolve for other users.<br>
<br>
Please note that while there is no limit on the number of requests a member organization may make for assistance, support provided through membership is geared toward helping people learn how to help themselves and there are limits to the complexity of issues that can be addressed. For example, membership does not include hosting, customization, data migration, or intensive data repair. We can provide you with strong guidance in these areas, but we can't undertake the solutions themselves for you. If your issue requires assistance beyond what is possible through membership, we will alert you to this and suggest alternatives.<br>
<br>
Please continue to file bug reports and feature requests via JIRA at <a href="http://support.archivesspace.org" rel="noreferrer" target="_blank">http://support.archivesspace.<wbr>org</a>. More information is available at <a href="https://archivesspace.atlassian.net/wiki/display/ADC/How+to+Report+a+Bug" rel="noreferrer" target="_blank">https://archivesspace.<wbr>atlassian.net/wiki/display/<wbr>ADC/How+to+Report+a+Bug</a> and <a href="https://archivesspace.atlassian.net/wiki/display/ADC/How+to+Request+a+New+Feature" rel="noreferrer" target="_blank">https://archivesspace.<wbr>atlassian.net/wiki/display/<wbr>ADC/How+to+Request+a+New+<wbr>Feature</a>. Program staff can assist you with filing these if you need help, or if a bug report or feature request comes out of your support request.<br>
<br>
We hope that you will find the availability of this additional level of technical assistance helpful. If you have any questions, or if you need assistance, please email the program team at <a href="mailto:ArchivesSpaceHome@lyrasis.org">ArchivesSpaceHome@lyrasis.org</a><<wbr>mailto:<a href="mailto:ArchivesSpaceHome@lyrasis.org">ArchivesSpaceHome@<wbr>lyrasis.org</a>>.<br>
Christine<br>
<br>
Christine Di Bella<br>
Community Outreach Manager<br>
<a href="mailto:christine.dibella@lyrasis.org">christine.dibella@lyrasis.org</a><<wbr>mailto:<a href="mailto:christine.dibella@lyrasis.org">christine.dibella@<wbr>lyrasis.org</a>><br>
<a href="tel:800.999.8558%20x2905" value="+18009998558">800.999.8558 x2905</a><br>
<a href="tel:678-235-2905" value="+16782352905">678-235-2905</a><br>
cdibella13 (Skype)<br>
[cid:image003.png@01CE734E.<wbr>FD759D30]<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20161114/ffeb11b2/attachment-0001.html" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>pipermail/archivesspace_users_<wbr>group/attachments/20161114/<wbr>ffeb11b2/attachment-0001.html</a>><br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: image001.png<br>
Type: image/png<br>
Size: 7645 bytes<br>
Desc: image001.png<br>
URL: <<a href="http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20161114/ffeb11b2/attachment-0001.png" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>pipermail/archivesspace_users_<wbr>group/attachments/20161114/<wbr>ffeb11b2/attachment-0001.png</a>><br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Mon, 14 Nov 2016 09:52:00 -0500<br>
From: Hong Jing <<a href="mailto:jennyjing@brandeis.edu">jennyjing@brandeis.edu</a>><br>
To: <a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a><br>
Subject: [Archivesspace_Users_Group] Job Posting: Digital Initiatives<br>
Librarian @ Brandeis University<br>
Message-ID:<br>
<CAMFN=<a href="mailto:HY%2B8KKyfw9yeNkkmBvADKtfbWHSzRGXV8598eDsWMBgkg@mail.gmail.com">HY+<wbr>8KKyfw9yeNkkmBvADKtfbWHSzRGXV8<wbr>598eDsWMBgkg@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
*Please excuse for cross-posting*<br>
<br>
<br>
*Job Posting: Digital Initiatives Librarian (Job ID: 525688)*<br>
<br>
Brandeis University seeks to hire a Digital Initiatives Librarian to be<br>
responsible for administration and configuration of institutional<br>
repository and related systems and applications.<br>
<br>
*Examples of Key Responsibilities:*<br>
<br>
- Responsible for administration and configuration of institutional<br>
repository and related systems and applications, including but not limited<br>
to creation of new IR communities and collections. Outreach to<br>
communities, for planning and performing batch loads of new collections,<br>
implementation of workflow, technical processes and methodology, and<br>
administering authorizations and roles within the institutional repository<br>
and related applications.<br>
- Works in conjunction with library systems staff, vendor support staff<br>
and open source communities, and Scholarly Communications to troubleshoot,<br>
resolve and escalate problems; works in conjunction with library systems<br>
staff to coordinate and perform application and system upgrades. Creates<br>
specifications and scripting for metadata transformation and crosswalks.<br>
- Performs technical support for faculty and staff in the use of the<br>
institutional repository and related applications, and assists with process<br>
and workflow development. Works as a member of the library team to plan<br>
and implement changes to delivered public interfaces; works as a member of<br>
the library team to integrate digital collections with other campus-wide<br>
applications.<br>
- Assists with creation of short and long-term plans for digitization of<br>
selected materials, working with content specialists and faculty members to<br>
determine priorities for digitization. Works as a member of Library &<br>
Technology Service (LTS) teams to assist faculty and staff in decision<br>
making for new collections. Receives requests for assistance with digital<br>
materials, and evaluates the appropriateness of those materials for<br>
inclusion in current or future digital asset systems.<br>
- Performs execution and support of LTS institutional repository<br>
policies and procedures, and assists in the development of policies as<br>
needed. Serves as resident authority for metadata and digitization<br>
standards. Helps guide and ensure adherence to capture standards, metadata<br>
standards, preservation standards, technical workflow and quality control.<br>
- Back-up core function of systems in the library and be available for<br>
on-call<br>
<br>
<br>
*Qualifications:*<br>
<br>
MLS or MSI degree from an ALA-accredited institution of higher education;<br>
3-5 years experience with library digital repositories<br>
<br>
Experience developing and managing digital software (DSpace,<br>
ArchivesSpace); knowledge and experience working in Unix or Linux systems<br>
at the CLI<br>
<br>
Proven engagement in the broader library systems community with a focus on<br>
administering and supporting digital initiatives applications and services;<br>
familiarity with metadata standards such as EAD, MARC, Dublic Core<br>
<br>
Strong organizational, communication, customer service and interpersonal<br>
skills; ability to work well with faculty, staff, and students.<br>
<br>
*Preferred skills:*<br>
<br>
Familiarity with digitization projects and standards for various materials,<br>
e.g. electronic theses and dissertations, manuscripts, photographs and<br>
audio and video recordings<br>
<br>
Experience with scripting languages and using APIs; experience with CSS,<br>
XML, XSL, XSLT and harvesting standards; experience in a research library<br>
or academic library<br>
<br>
<br>
*How to Apply:*<br>
<br>
Submit cover letter and resume as a single document at<br>
<a href="http://www.brandeis.edu/humanresources/jobs/external.html" rel="noreferrer" target="_blank">http://www.brandeis.edu/<wbr>humanresources/jobs/external.<wbr>html</a>. Elect option<br>
for "External Applicant". Sort the job listing by clicking the *Job<br>
ID* column<br>
heading. Locate the desired job listing by Job ID. Click the job title<br>
and then Apply Now.<br>
<br>
<br>
*Closing Statement:*<br>
<br>
Brandeis University is an affirmative action/equal opportunity employer and<br>
encourages minorities, women, disabled individuals, and eligible veterans<br>
to apply. It is the policy of the University not to discriminate against<br>
any applicant or employee on the basis of race, ancestry, color, religion,<br>
sex, sexual orientation, age, genetic information, national origin,<br>
disability, veteran status, or on the basis of any other legally protected<br>
category.<br>
<br>
--<br>
Jenny Jing<br>
<br>
Manager, Library Systems<br>
Library & Technology Services,<br>
Brandeis University Library<br>
<br>
<a href="tel:781-736-4698" value="+17817364698">781-736-4698</a><br>
<a href="mailto:JennyJing@brandeis.edu">JennyJing@brandeis.edu</a><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20161114/9596dc4d/attachment-0001.html" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>pipermail/archivesspace_users_<wbr>group/attachments/20161114/<wbr>9596dc4d/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 7<br>
Date: Tue, 15 Nov 2016 13:56:15 +0000<br>
From: ArchivesSpaceHome <<a href="mailto:ArchivesSpaceHome@lyrasis.org">ArchivesSpaceHome@lyrasis.org</a><wbr>><br>
To: Archivesspace Users Group<br>
<<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a>><br>
Subject: [Archivesspace_Users_Group] Job posting for Vanderbilt<br>
University<br>
Message-ID:<br>
<<a href="mailto:DM2PR0801MB0848D4E2205EF8D204522EF6F1BF0@DM2PR0801MB0848.namprd08.prod.outlook.com">DM2PR0801MB0848D4E2205EF8D204<wbr>522EF6F1BF0@DM2PR0801MB0848.<wbr>namprd08.prod.outlook.com</a>><br>
<br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
Posted on behalf of Valerie Hotchkiss.<br>
<br>
From: Hotchkiss, Valerie [mailto:<a href="mailto:valerie.hotchkiss@vanderbilt.edu">valerie.hotchkiss@<wbr>vanderbilt.edu</a>]<br>
Sent: Monday, November 14, 2016 2:53 PM<br>
To: ArchivesSpaceHome <<a href="mailto:ArchivesSpaceHome@lyrasis.org">ArchivesSpaceHome@lyrasis.org</a><wbr>><br>
Subject: Job posting<br>
<br>
Dear Archives Space colleagues,<br>
<br>
Since this job description specifically entails introducing ArchivesSpace at Vanderbilt, I wonder if you can help us spread the word about it?<br>
<a href="https://vanderuniv.taleo.net/careersection/.vu_cs/jobdetail.ftl?job=1605657" rel="noreferrer" target="_blank">https://vanderuniv.taleo.net/<wbr>careersection/.vu_cs/<wbr>jobdetail.ftl?job=1605657</a><br>
<br>
Many thanks,<br>
v<br>
<br>
Valerie Hotchkiss<br>
University Librarian<br>
The Jean and Alexander Heard Library<<a href="http://www.library.vanderbilt.edu/" rel="noreferrer" target="_blank">http://www.library.<wbr>vanderbilt.edu/</a>><br>
Vanderbilt University<br>
<a href="tel:%28615%29%20322-4782" value="+16153224782">(615) 322-4782</a><br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20161115/5444b374/attachment-0001.html" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>pipermail/archivesspace_users_<wbr>group/attachments/20161115/<wbr>5444b374/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 8<br>
Date: Tue, 15 Nov 2016 12:34:55 -0500<br>
From: Cheri Crist <<a href="mailto:ccrist@eastman.org">ccrist@eastman.org</a>><br>
To: <a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a><br>
Subject: [Archivesspace_Users_Group] DACS 7.1.6 equivalent in<br>
ArchivesSpace<br>
Message-ID:<br>
<CAGmhTeNHR5u_<wbr>t2H8hB3Eg6ynv28Lta=<a href="mailto:AQFVXEmfHf031MF3dvA@mail.gmail.com">AQFVXEmfHf0<wbr>31MF3dvA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi list,<br>
<br>
I'm finding that somewhere in the annals of time, individual pieces of<br>
ephemera were given museum object numbers in TMS, and these numbers are<br>
written on the items. I'm wondering if anyone out there has a best practice<br>
for recording these numbers in AS. I thought recording the TMS number in<br>
the Component Unique Identifier field at item level would work, but it<br>
doesn't show up in the pdf. (It does show in the public interface,<br>
however.) What have other people done?<br>
<br>
Thanks,<br>
Cheri<br>
<br>
<br>
Cheri Crist<br>
Project Archivist<br>
Richard and Ronay Menschel Library<br>
George Eastman Museum<br>
900 East Ave.<br>
Rochester, NY 14607<br>
<a href="mailto:ccrist@eastman.org">ccrist@eastman.org</a><br>
<a href="tel:%28585%29271-3361%20ext.%20280" value="+15852713361">(585)271-3361 ext. 280</a><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20161115/7ae31a86/attachment-0001.html" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>pipermail/archivesspace_users_<wbr>group/attachments/20161115/<wbr>7ae31a86/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 9<br>
Date: Tue, 15 Nov 2016 14:37:56 -0500<br>
From: Sally Vermaaten <<a href="mailto:sally.vermaaten@nyu.edu">sally.vermaaten@nyu.edu</a>><br>
To: <a href="mailto:archivesspace@googlegroups.com">archivesspace@googlegroups.com</a><wbr>, Archivesspace Users Group<br>
<<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a>><br>
Subject: [Archivesspace_Users_Group] Problems working with archival<br>
object with large number of direct children<br>
Message-ID:<br>
<<a href="mailto:CALt9ybsGYKTab7ESLLCxZ6qCk64TXr3ysZzqdiPXN0WomXzAWA@mail.gmail.com">CALt9ybsGYKTab7ESLLCxZ6qCk64T<wbr>Xr3ysZzqdiPXN0WomXzAWA@mail.<wbr>gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi everyone,<br>
<br>
We're running into an issue with a large resource record in ArchivesSpace<br>
and wonder if anyone has experienced a similar issue. In one resource<br>
record, we have a series/archival object with around 19,000 direct<br>
children/archival objects. We've found that:<br>
<br>
- it takes several minutes to open the series in the 'tree' navigation<br>
view and then, once opened scrolling through series is very slow / laggy<br>
- it takes a couple of minutes to open any archival object in the series<br>
in edit mode and<br>
- it takes a couple of minutes to save changes to any archival object<br>
within the series<br>
<br>
Does anyone else have a similarly large archival object in a resource<br>
record? If so, have you observed the same long load/save time when editing<br>
the component records?<br>
<br>
The slow load time does not seem to be affected by memory allocation; we've<br>
tried increasing the speed / size of the server and it seemed to have no<br>
effect. We'd definitely appreciate any other suggestions for how we might<br>
fix or work around the problem.<br>
<br>
We also wonder if this performance issue is essentially caused by the<br>
queries being run to generate the UI view - i.e. perhaps in generating the<br>
resource 'tree' view, all data for the whole series (all 19k archival<br>
objects) is being retrieved and stored in memory? If so, we wondered if it<br>
would be possible and would make sense to change the queries running during<br>
tree generation, etc. to only retrieve some batches at a time, lazy loading<br>
style?<br>
<br>
Thanks,<br>
Weatherly and Sally<br>
<br>
--<br>
Sally Vermaaten<br>
Project Manager, Archival Systems<br>
New York University Libraries<br>
<a href="tel:1-212-992-6259" value="+12129926259">1-212-992-6259</a><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20161115/f4355ae5/attachment-0001.html" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>pipermail/archivesspace_users_<wbr>group/attachments/20161115/<wbr>f4355ae5/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 10<br>
Date: Tue, 15 Nov 2016 19:46:25 +0000<br>
From: "Runyon, Carolyn" <<a href="mailto:Carolyn-Runyon@utc.edu">Carolyn-Runyon@utc.edu</a>><br>
To: "<a href="mailto:archivesspace@googlegroups.com">archivesspace@googlegroups.<wbr>com</a>" <<a href="mailto:archivesspace@googlegroups.com">archivesspace@googlegroups.<wbr>com</a>>,<br>
Archivesspace Users Group<br>
<<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a>><br>
Subject: Re: [Archivesspace_Users_Group] [archivesspace] Problems<br>
working with archival object with large number of direct children<br>
Message-ID: <<a href="mailto:A53D9B54-61F9-4CE9-9208-C03808A87914@utc.edu">A53D9B54-61F9-4CE9-9208-<wbr>C03808A87914@utc.edu</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
We have noticed this as well. In fact, one of our resource records is large enough that it won?t open on the staff interface at all.<br>
<br>
Carolyn Runyon<br>
Assistant Head of Collection Services and Director of Special Collections<br>
University of Tennessee at Chattanooga Library<br>
615 McCallie Ave., Chattanooga, TN 37403<br>
<a href="mailto:Carolyn-Runyon@utc.edu">Carolyn-Runyon@utc.edu</a><mailto:<a href="mailto:Carolyn-Runyon@utc.edu"><wbr>Carolyn-Runyon@utc.edu</a>>, <a href="tel:%28423%29%20425-4503" value="+14234254503">(423) 425-4503</a><br>
Dept. 6456, LIB 439D<br>
<br>
On Nov 15, 2016, at 2:37 PM, Sally Vermaaten <<a href="mailto:sally.vermaaten@nyu.edu">sally.vermaaten@nyu.edu</a><<wbr>mailto:<a href="mailto:sally.vermaaten@nyu.edu">sally.vermaaten@nyu.edu</a><wbr>>> wrote:<br>
<br>
Hi everyone,<br>
<br>
We're running into an issue with a large resource record in ArchivesSpace and wonder if anyone has experienced a similar issue. In one resource record, we have a series/archival object with around 19,000 direct children/archival objects. We've found that:<br>
<br>
* it takes several minutes to open the series in the 'tree' navigation view and then, once opened scrolling through series is very slow / laggy<br>
* it takes a couple of minutes to open any archival object in the series in edit mode and<br>
* it takes a couple of minutes to save changes to any archival object within the series<br>
<br>
Does anyone else have a similarly large archival object in a resource record? If so, have you observed the same long load/save time when editing the component records?<br>
<br>
The slow load time does not seem to be affected by memory allocation; we've tried increasing the speed / size of the server and it seemed to have no effect. We'd definitely appreciate any other suggestions for how we might fix or work around the problem.<br>
<br>
We also wonder if this performance issue is essentially caused by the queries being run to generate the UI view - i.e. perhaps in generating the resource 'tree' view, all data for the whole series (all 19k archival objects) is being retrieved and stored in memory? If so, we wondered if it would be possible and would make sense to change the queries running during tree generation, etc. to only retrieve some batches at a time, lazy loading style?<br>
<br>
Thanks,<br>
Weatherly and Sally<br>
<br>
--<br>
Sally Vermaaten<br>
Project Manager, Archival Systems<br>
New York University Libraries<br>
<a href="tel:1-212-992-6259" value="+12129926259">1-212-992-6259</a><br>
<br>
--<br>
You received this message because you are subscribed to the Google Groups "ArchivesSpace" group.<br>
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="mailto:archivesspace%2Bunsubscribe@googlegroups.com">archivesspace+unsubscribe@<wbr>googlegroups.com</a><mailto:<a href="mailto:archivesspace%2Bunsubscribe@googlegroups.com">archiv<wbr>esspace+unsubscribe@<wbr>googlegroups.com</a>>.<br>
For more options, visit <a href="https://groups.google.com/d/optout" rel="noreferrer" target="_blank">https://groups.google.com/d/<wbr>optout</a>.<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20161115/987641d9/attachment-0001.html" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>pipermail/archivesspace_users_<wbr>group/attachments/20161115/<wbr>987641d9/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 11<br>
Date: Tue, 15 Nov 2016 19:49:02 +0000<br>
From: Ryan Edwards <<a href="mailto:REedwards@getty.edu">REedwards@getty.edu</a>><br>
To: Archivesspace Users Group<br>
<<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a>>,<br>
"<a href="mailto:archivesspace@googlegroups.com">archivesspace@googlegroups.<wbr>com</a>" <<a href="mailto:archivesspace@googlegroups.com">archivesspace@googlegroups.<wbr>com</a>><br>
Subject: Re: [Archivesspace_Users_Group] Problems working with<br>
archival object with large number of direct children<br>
Message-ID:<br>
<<a href="mailto:DM5PR05MB3244D4492CCBD4DE4817C07CBEBF0@DM5PR05MB3244.namprd05.prod.outlook.com">DM5PR05MB3244D4492CCBD4DE4817<wbr>C07CBEBF0@DM5PR05MB3244.<wbr>namprd05.prod.outlook.com</a>><br>
<br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hello Sally,<br>
<br>
We?ve also noticed that it can take a while (2-3 minutes) to load one of our largest resources, even after we increased the physical RAM on our server.<br>
<br>
-Ryan<br>
<br>
Ryan Edwards<br>
Digital Access and Systems Librarian<br>
Getty Research Institute<br>
<br>
From: <a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-<wbr>bounces@lyralists.lyrasis.org</a> [mailto:<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_<wbr>group-bounces@lyralists.<wbr>lyrasis.org</a>] On Behalf Of Sally Vermaaten<br>
Sent: Tuesday, November 15, 2016 11:38 AM<br>
To: <a href="mailto:archivesspace@googlegroups.com">archivesspace@googlegroups.com</a><wbr>; Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a>><br>
Subject: [Archivesspace_Users_Group] Problems working with archival object with large number of direct children<br>
<br>
Hi everyone,<br>
<br>
We're running into an issue with a large resource record in ArchivesSpace and wonder if anyone has experienced a similar issue. In one resource record, we have a series/archival object with around 19,000 direct children/archival objects. We've found that:<br>
? it takes several minutes to open the series in the 'tree' navigation view and then, once opened scrolling through series is very slow / laggy<br>
? it takes a couple of minutes to open any archival object in the series in edit mode and<br>
? it takes a couple of minutes to save changes to any archival object within the series<br>
Does anyone else have a similarly large archival object in a resource record? If so, have you observed the same long load/save time when editing the component records?<br>
<br>
The slow load time does not seem to be affected by memory allocation; we've tried increasing the speed / size of the server and it seemed to have no effect. We'd definitely appreciate any other suggestions for how we might fix or work around the problem.<br>
<br>
We also wonder if this performance issue is essentially caused by the queries being run to generate the UI view - i.e. perhaps in generating the resource 'tree' view, all data for the whole series (all 19k archival objects) is being retrieved and stored in memory? If so, we wondered if it would be possible and would make sense to change the queries running during tree generation, etc. to only retrieve some batches at a time, lazy loading style?<br>
<br>
Thanks,<br>
Weatherly and Sally<br>
<br>
--<br>
Sally Vermaaten<br>
Project Manager, Archival Systems<br>
New York University Libraries<br>
1-212-992-6259<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20161115/255cb23a/attachment-0001.html" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>pipermail/archivesspace_users_<wbr>group/attachments/20161115/<wbr>255cb23a/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 12<br>
Date: Tue, 15 Nov 2016 15:25:20 -0500<br>
From: Jason Loeffler <<a href="mailto:j@minorscience.com">j@minorscience.com</a>><br>
To: Archivesspace Users Group<br>
<<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a>><br>
Cc: <a href="mailto:archivesspace@googlegroups.com">archivesspace@googlegroups.com</a><br>
Subject: Re: [Archivesspace_Users_Group] Problems working with<br>
archival object with large number of direct children<br>
Message-ID:<br>
<<a href="mailto:CAP4gJsW_9wbo6ZvzXAJq1cFaP-CK47hwNow8AEBfa_P5Ffj_iA@mail.gmail.com">CAP4gJsW_9wbo6ZvzXAJq1cFaP-<wbr>CK47hwNow8AEBfa_P5Ffj_iA@mail.<wbr>gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi Sally,<br>
<br>
Definitely, yes. We have many resources with 5,000 or more archival object<br>
records. We've deployed on some pretty decent Amazon EC2 boxes (16GB<br>
memory, burstable CPU, etc.) with negligible improvement. I have a feeling<br>
that this is not a resource allocation issue. Looking at the web inspector,<br>
most of the time is spent negotiating jstree <<a href="http://jstree.com/" rel="noreferrer" target="_blank">http://jstree.com/</a>> and/or<br>
loading* all JSON objects* associated with a resource into the browser.<br>
Maybe an ASpace dev can weigh in.<br>
<br>
>From the sysadmin side, Maureen Callahan at Yale commissioned Percona to<br>
evaluate ArchivesSpace and MySQL performance. I've attached the report. Let<br>
me know if you need any help interpreting the report.<br>
<br>
At some point, and quite apart from this thread, I hope we can collectively<br>
revisit the staff interface architecture and recommend improvements.<br>
<br>
JL<br>
<br>
On Tue, Nov 15, 2016 at 2:37 PM, Sally Vermaaten <<a href="mailto:sally.vermaaten@nyu.edu">sally.vermaaten@nyu.edu</a>><br>
wrote:<br>
<br>
> Hi everyone,<br>
><br>
> We're running into an issue with a large resource record in ArchivesSpace<br>
> and wonder if anyone has experienced a similar issue. In one resource<br>
> record, we have a series/archival object with around 19,000 direct<br>
> children/archival objects. We've found that:<br>
><br>
> - it takes several minutes to open the series in the 'tree' navigation<br>
> view and then, once opened scrolling through series is very slow / laggy<br>
> - it takes a couple of minutes to open any archival object in the<br>
> series in edit mode and<br>
> - it takes a couple of minutes to save changes to any archival object<br>
> within the series<br>
><br>
> Does anyone else have a similarly large archival object in a resource<br>
> record? If so, have you observed the same long load/save time when editing<br>
> the component records?<br>
><br>
> The slow load time does not seem to be affected by memory allocation;<br>
> we've tried increasing the speed / size of the server and it seemed to have<br>
> no effect. We'd definitely appreciate any other suggestions for how we<br>
> might fix or work around the problem.<br>
><br>
> We also wonder if this performance issue is essentially caused by the<br>
> queries being run to generate the UI view - i.e. perhaps in generating the<br>
> resource 'tree' view, all data for the whole series (all 19k archival<br>
> objects) is being retrieved and stored in memory? If so, we wondered if it<br>
> would be possible and would make sense to change the queries running during<br>
> tree generation, etc. to only retrieve some batches at a time, lazy loading<br>
> style?<br>
><br>
> Thanks,<br>
> Weatherly and Sally<br>
><br>
> --<br>
> Sally Vermaaten<br>
> Project Manager, Archival Systems<br>
> New York University Libraries<br>
> 1-212-992-6259<br>
><br>
> ______________________________<wbr>_________________<br>
> Archivesspace_Users_Group mailing list<br>
> <a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a><br>
> <a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>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/20161115/41bbc85b/attachment-0001.html" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>pipermail/archivesspace_users_<wbr>group/attachments/20161115/<wbr>41bbc85b/attachment-0001.html</a>><br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: report.pdf<br>
Type: application/pdf<br>
Size: 81907 bytes<br>
Desc: not available<br>
URL: <<a href="http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20161115/41bbc85b/attachment-0001.pdf" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>pipermail/archivesspace_users_<wbr>group/attachments/20161115/<wbr>41bbc85b/attachment-0001.pdf</a>><br>
<br>
------------------------------<br>
<br>
Message: 13<br>
Date: Tue, 15 Nov 2016 15:35:06 -0500<br>
From: Jason Loeffler <<a href="mailto:j@minorscience.com">j@minorscience.com</a>><br>
To: Archivesspace Users Group<br>
<<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a>><br>
Cc: <a href="mailto:archivesspace@googlegroups.com">archivesspace@googlegroups.com</a><br>
Subject: Re: [Archivesspace_Users_Group] Problems working with<br>
archival object with large number of direct children<br>
Message-ID:<br>
<<a href="mailto:CAP4gJsX8HimVyaPCha-PSfRhRO44erMm9Tv-8AwO-DqrHf3kHA@mail.gmail.com">CAP4gJsX8HimVyaPCha-<wbr>PSfRhRO44erMm9Tv-8AwO-<wbr>DqrHf3kHA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
I should add that application performance was a hot topic in August last<br>
year. Some of the issues described have been mitigated and/or implemented;<br>
others not so much.<br>
<br>
<a href="http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/2015-August/002285.html" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>pipermail/archivesspace_users_<wbr>group/2015-August/002285.html</a><br>
<a href="http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/2015-August/002319.html" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>pipermail/archivesspace_users_<wbr>group/2015-August/002319.html</a><br>
<a href="http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/2015-August/002346.html" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>pipermail/archivesspace_users_<wbr>group/2015-August/002346.html</a><br>
<br>
On Tue, Nov 15, 2016 at 3:25 PM, Jason Loeffler <<a href="mailto:j@minorscience.com">j@minorscience.com</a>> wrote:<br>
<br>
> Hi Sally,<br>
><br>
> Definitely, yes. We have many resources with 5,000 or more archival object<br>
> records. We've deployed on some pretty decent Amazon EC2 boxes (16GB<br>
> memory, burstable CPU, etc.) with negligible improvement. I have a feeling<br>
> that this is not a resource allocation issue. Looking at the web inspector,<br>
> most of the time is spent negotiating jstree <<a href="http://jstree.com/" rel="noreferrer" target="_blank">http://jstree.com/</a>> and/or<br>
> loading* all JSON objects* associated with a resource into the browser.<br>
> Maybe an ASpace dev can weigh in.<br>
><br>
> From the sysadmin side, Maureen Callahan at Yale commissioned Percona to<br>
> evaluate ArchivesSpace and MySQL performance. I've attached the report. Let<br>
> me know if you need any help interpreting the report.<br>
><br>
> At some point, and quite apart from this thread, I hope we can<br>
> collectively revisit the staff interface architecture and recommend<br>
> improvements.<br>
><br>
> JL<br>
><br>
> On Tue, Nov 15, 2016 at 2:37 PM, Sally Vermaaten <<a href="mailto:sally.vermaaten@nyu.edu">sally.vermaaten@nyu.edu</a>><br>
> wrote:<br>
><br>
>> Hi everyone,<br>
>><br>
>> We're running into an issue with a large resource record in ArchivesSpace<br>
>> and wonder if anyone has experienced a similar issue. In one resource<br>
>> record, we have a series/archival object with around 19,000 direct<br>
>> children/archival objects. We've found that:<br>
>><br>
>> - it takes several minutes to open the series in the 'tree'<br>
>> navigation view and then, once opened scrolling through series is very slow<br>
>> / laggy<br>
>> - it takes a couple of minutes to open any archival object in the<br>
>> series in edit mode and<br>
>> - it takes a couple of minutes to save changes to any archival object<br>
>> within the series<br>
>><br>
>> Does anyone else have a similarly large archival object in a resource<br>
>> record? If so, have you observed the same long load/save time when editing<br>
>> the component records?<br>
>><br>
>> The slow load time does not seem to be affected by memory allocation;<br>
>> we've tried increasing the speed / size of the server and it seemed to have<br>
>> no effect. We'd definitely appreciate any other suggestions for how we<br>
>> might fix or work around the problem.<br>
>><br>
>> We also wonder if this performance issue is essentially caused by the<br>
>> queries being run to generate the UI view - i.e. perhaps in generating the<br>
>> resource 'tree' view, all data for the whole series (all 19k archival<br>
>> objects) is being retrieved and stored in memory? If so, we wondered if it<br>
>> would be possible and would make sense to change the queries running during<br>
>> tree generation, etc. to only retrieve some batches at a time, lazy loading<br>
>> style?<br>
>><br>
>> Thanks,<br>
>> Weatherly and Sally<br>
>><br>
>> --<br>
>> Sally Vermaaten<br>
>> Project Manager, Archival Systems<br>
>> New York University Libraries<br>
>> 1-212-992-6259<br>
>><br>
>> ______________________________<wbr>_________________<br>
>> Archivesspace_Users_Group mailing list<br>
>> <a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a><br>
>> <a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a><br>
>><br>
>><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20161115/e441cee3/attachment-0001.html" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>pipermail/archivesspace_users_<wbr>group/attachments/20161115/<wbr>e441cee3/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 14<br>
Date: Tue, 15 Nov 2016 20:46:44 +0000<br>
From: "Joshua D. Shaw" <<a href="mailto:Joshua.D.Shaw@dartmouth.edu">Joshua.D.Shaw@dartmouth.edu</a>><br>
To: Archivesspace Users Group<br>
<<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a>><br>
Subject: Re: [Archivesspace_Users_Group] Problems working with<br>
archival object with large number of direct children<br>
Message-ID: <<a href="mailto:44F19B6F-CD13-43C6-A494-92223359C987@dartmouth.edu">44F19B6F-CD13-43C6-A494-<wbr>92223359C987@dartmouth.edu</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi all ?<br>
<br>
We at Dartmouth have experienced similar issues. We have some large resources as well (one has 60K+ objects in the tree) and anything that involves a save or rearrangement (moving a file around, etc) can take a *lot* of time (many minutes) and may cause an error ? typically of the ?another user is modifying this record? type.<br>
<br>
If we have to do any modifications to a resource of that size, we a) budget a lot of time and b) do things in small increments ? ie don?t move more than a couple of files around at a time. It?s not a great solution, but it does minimize some of the headache.<br>
<br>
I *think* (but haven?t had the time to really dig into this) that one reason the error comes about is because the indexer steps on/collides with the process that the save/arrangement kicked off. We are still running 1.3 and hope that some of our issues will be mitigated when we move to 1.5.1, though we know that not all of them have been resolved yet.<br>
<br>
One other data point is that we?ve got a plugin that runs as a background job doing a bunch of importing. This background job touches some of the larger resources, but does *not* cause the errors and long save times, which leads me to believe that a lot of the problem is in the frontend ? perhaps with the way the tree is populated - as Jason pointed out.<br>
<br>
Best,<br>
Joshua<br>
<br>
From: <<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-<wbr>bounces@lyralists.lyrasis.org</a>> on behalf of Jason Loeffler <<a href="mailto:j@minorscience.com">j@minorscience.com</a>><br>
Reply-To: Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a>><br>
Date: Tuesday, November 15, 2016 at 3:25 PM<br>
To: Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a>><br>
Cc: "<a href="mailto:archivesspace@googlegroups.com">archivesspace@googlegroups.<wbr>com</a>" <<a href="mailto:archivesspace@googlegroups.com">archivesspace@googlegroups.<wbr>com</a>><br>
Subject: Re: [Archivesspace_Users_Group] Problems working with archival object with large number of direct children<br>
<br>
Hi Sally,<br>
<br>
Definitely, yes. We have many resources with 5,000 or more archival object records. We've deployed on some pretty decent Amazon EC2 boxes (16GB memory, burstable CPU, etc.) with negligible improvement. I have a feeling that this is not a resource allocation issue. Looking at the web inspector, most of the time is spent negotiating jstree<<a href="http://jstree.com/" rel="noreferrer" target="_blank">http://jstree.com/</a>> and/or loading all JSON objects associated with a resource into the browser. Maybe an ASpace dev can weigh in.<br>
<br>
<br>
>From the sysadmin side, Maureen Callahan at Yale commissioned Percona to evaluate ArchivesSpace and MySQL performance. I've attached the report. Let me know if you need any help interpreting the report.<br>
<br>
At some point, and quite apart from this thread, I hope we can collectively revisit the staff interface architecture and recommend improvements.<br>
<br>
JL<br>
<br>
On Tue, Nov 15, 2016 at 2:37 PM, Sally Vermaaten <<a href="mailto:sally.vermaaten@nyu.edu">sally.vermaaten@nyu.edu</a><<wbr>mailto:<a href="mailto:sally.vermaaten@nyu.edu">sally.vermaaten@nyu.edu</a><wbr>>> wrote:<br>
Hi everyone,<br>
<br>
We're running into an issue with a large resource record in ArchivesSpace and wonder if anyone has experienced a similar issue. In one resource record, we have a series/archival object with around 19,000 direct children/archival objects. We've found that:<br>
? it takes several minutes to open the series in the 'tree' navigation view and then, once opened scrolling through series is very slow / laggy<br>
? it takes a couple of minutes to open any archival object in the series in edit mode and<br>
? it takes a couple of minutes to save changes to any archival object within the series<br>
Does anyone else have a similarly large archival object in a resource record? If so, have you observed the same long load/save time when editing the component records?<br>
<br>
The slow load time does not seem to be affected by memory allocation; we've tried increasing the speed / size of the server and it seemed to have no effect. We'd definitely appreciate any other suggestions for how we might fix or work around the problem.<br>
<br>
We also wonder if this performance issue is essentially caused by the queries being run to generate the UI view - i.e. perhaps in generating the resource 'tree' view, all data for the whole series (all 19k archival objects) is being retrieved and stored in memory? If so, we wondered if it would be possible and would make sense to change the queries running during tree generation, etc. to only retrieve some batches at a time, lazy loading style?<br>
<br>
Thanks,<br>
Weatherly and Sally<br>
<br>
--<br>
Sally Vermaaten<br>
Project Manager, Archival Systems<br>
New York University Libraries<br>
1-212-992-6259<tel:1-212-992-<wbr>6259><br>
<br>
______________________________<wbr>_________________<br>
Archivesspace_Users_Group mailing list<br>
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a><mailto:<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">A<wbr>rchivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a>><br>
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a><br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20161115/f1ff16f0/attachment-0001.html" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>pipermail/archivesspace_users_<wbr>group/attachments/20161115/<wbr>f1ff16f0/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 15<br>
Date: Wed, 16 Nov 2016 10:17:37 +1100<br>
From: James Bullen <<a href="mailto:james@hudmol.com">james@hudmol.com</a>><br>
To: Archivesspace Users Group<br>
<<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a>>,<br>
<a href="mailto:archivesspace@googlegroups.com">archivesspace@googlegroups.com</a><br>
Subject: Re: [Archivesspace_Users_Group] Problems working with<br>
archival object with large number of direct children<br>
Message-ID: <<a href="mailto:404DE50A-B8DD-4A4D-B14A-FDDED5B64D57@hudmol.com">404DE50A-B8DD-4A4D-B14A-<wbr>FDDED5B64D57@hudmol.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
<br>
Hi all,<br>
<br>
As part of our new role as ArchivesSpace development partner, we will be addressing issues like this as a priority.<br>
<br>
It is still early days and we?re working with the folks at the ArchivesSpace program on a release schedule, so we can?t make any definitive statements yet, but please know that we are aware of this issue and will address it as soon as we are able.<br>
<br>
<br>
Cheers,<br>
James<br>
<br>
<br>
?<br>
James Bullen<br>
Hudson Molonglo<br>
<br>
<br>
<br>
> On Nov 16, 2016, at 7:46 AM, Joshua D. Shaw <<a href="mailto:Joshua.D.Shaw@dartmouth.edu">Joshua.D.Shaw@dartmouth.edu</a>> wrote:<br>
><br>
> Hi all ?<br>
><br>
> We at Dartmouth have experienced similar issues. We have some large resources as well (one has 60K+ objects in the tree) and anything that involves a save or rearrangement (moving a file around, etc) can take a *lot* of time (many minutes) and may cause an error ? typically of the ?another user is modifying this record? type.<br>
><br>
> If we have to do any modifications to a resource of that size, we a) budget a lot of time and b) do things in small increments ? ie don?t move more than a couple of files around at a time. It?s not a great solution, but it does minimize some of the headache.<br>
><br>
> I *think* (but haven?t had the time to really dig into this) that one reason the error comes about is because the indexer steps on/collides with the process that the save/arrangement kicked off. We are still running 1.3 and hope that some of our issues will be mitigated when we move to 1.5.1, though we know that not all of them have been resolved yet.<br>
><br>
> One other data point is that we?ve got a plugin that runs as a background job doing a bunch of importing. This background job touches some of the larger resources, but does *not* cause the errors and long save times, which leads me to believe that a lot of the problem is in the frontend ? perhaps with the way the tree is populated - as Jason pointed out.<br>
><br>
> Best,<br>
> Joshua<br>
><br>
> From: <<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-<wbr>bounces@lyralists.lyrasis.org</a> <mailto:<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_<wbr>group-bounces@lyralists.<wbr>lyrasis.org</a>>> on behalf of Jason Loeffler <<a href="mailto:j@minorscience.com">j@minorscience.com</a> <mailto:<a href="mailto:j@minorscience.com">j@minorscience.com</a>>><br>
> Reply-To: Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a> <mailto:<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_<wbr>group@lyralists.lyrasis.org</a>>><br>
> Date: Tuesday, November 15, 2016 at 3:25 PM<br>
> To: Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a> <mailto:<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_<wbr>group@lyralists.lyrasis.org</a>>><br>
> Cc: "<a href="mailto:archivesspace@googlegroups.com">archivesspace@googlegroups.<wbr>com</a> <mailto:<a href="mailto:archivesspace@googlegroups.com">archivesspace@<wbr>googlegroups.com</a>>" <<a href="mailto:archivesspace@googlegroups.com">archivesspace@googlegroups.<wbr>com</a> <mailto:<a href="mailto:archivesspace@googlegroups.com">archivesspace@<wbr>googlegroups.com</a>>><br>
> Subject: Re: [Archivesspace_Users_Group] Problems working with archival object with large number of direct children<br>
><br>
> Hi Sally,<br>
><br>
> Definitely, yes. We have many resources with 5,000 or more archival object records. We've deployed on some pretty decent Amazon EC2 boxes (16GB memory, burstable CPU, etc.) with negligible improvement. I have a feeling that this is not a resource allocation issue. Looking at the web inspector, most of the time is spent negotiating jstree <<a href="http://jstree.com/" rel="noreferrer" target="_blank">http://jstree.com/</a>> and/or loading all JSON objects associated with a resource into the browser. Maybe an ASpace dev can weigh in.<br>
><br>
><br>
> From the sysadmin side, Maureen Callahan at Yale commissioned Percona to evaluate ArchivesSpace and MySQL performance. I've attached the report. Let me know if you need any help interpreting the report.<br>
><br>
> At some point, and quite apart from this thread, I hope we can collectively revisit the staff interface architecture and recommend improvements.<br>
><br>
> JL<br>
><br>
> On Tue, Nov 15, 2016 at 2:37 PM, Sally Vermaaten <<a href="mailto:sally.vermaaten@nyu.edu">sally.vermaaten@nyu.edu</a> <mailto:<a href="mailto:sally.vermaaten@nyu.edu">sally.vermaaten@nyu.<wbr>edu</a>>> wrote:<br>
>> Hi everyone,<br>
>><br>
>> We're running into an issue with a large resource record in ArchivesSpace and wonder if anyone has experienced a similar issue. In one resource record, we have a series/archival object with around 19,000 direct children/archival objects. We've found that:<br>
>> ? it takes several minutes to open the series in the 'tree' navigation view and then, once opened scrolling through series is very slow / laggy<br>
>> ? it takes a couple of minutes to open any archival object in the series in edit mode and<br>
>> ? it takes a couple of minutes to save changes to any archival object within the series<br>
>> Does anyone else have a similarly large archival object in a resource record? If so, have you observed the same long load/save time when editing the component records?<br>
>><br>
>> The slow load time does not seem to be affected by memory allocation; we've tried increasing the speed / size of the server and it seemed to have no effect. We'd definitely appreciate any other suggestions for how we might fix or work around the problem.<br>
>><br>
>> We also wonder if this performance issue is essentially caused by the queries being run to generate the UI view - i.e. perhaps in generating the resource 'tree' view, all data for the whole series (all 19k archival objects) is being retrieved and stored in memory? If so, we wondered if it would be possible and would make sense to change the queries running during tree generation, etc. to only retrieve some batches at a time, lazy loading style?<br>
>><br>
>> Thanks,<br>
>> Weatherly and Sally<br>
>><br>
>> --<br>
>> Sally Vermaaten<br>
>> Project Manager, Archival Systems<br>
>> New York University Libraries<br>
>> 1-212-992-6259 <tel:1-212-992-6259><br>
>><br>
>> ______________________________<wbr>_________________<br>
>> Archivesspace_Users_Group mailing list<br>
>> <a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a> <mailto:<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_<wbr>Group@lyralists.lyrasis.org</a>><br>
>> <a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a> <<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a>><br>
><br>
> !DSPAM:<wbr>582b7444314351074817778! ______________________________<wbr>_________________<br>
> Archivesspace_Users_Group mailing list<br>
> <a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a> <mailto:<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_<wbr>Group@lyralists.lyrasis.org</a>><br>
> <a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a> <<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a>><br>
><br>
><br>
> !DSPAM:<wbr>582b7444314351074817778!<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20161116/4054a705/attachment-0001.html" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>pipermail/archivesspace_users_<wbr>group/attachments/20161116/<wbr>4054a705/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 16<br>
Date: Tue, 15 Nov 2016 18:28:44 -0500<br>
From: Jason Loeffler <<a href="mailto:j@minorscience.com">j@minorscience.com</a>><br>
To: Archivesspace Users Group<br>
<<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a>><br>
Cc: <a href="mailto:archivesspace@googlegroups.com">archivesspace@googlegroups.com</a><br>
Subject: Re: [Archivesspace_Users_Group] Problems working with<br>
archival object with large number of direct children<br>
Message-ID:<br>
<<a href="mailto:CAP4gJsVcnku_79ParxD4j-s88z7-6G8HdywDRHRZwVWWM_RMBw@mail.gmail.com">CAP4gJsVcnku_79ParxD4j-s88z7-<wbr>6G8HdywDRHRZwVWWM_RMBw@mail.<wbr>gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Thanks so much, James. Can you tell me if there's a script available for<br>
generating an arbitrary number of test records? Something similar to<br>
Drupal's devel generate <<a href="https://api.drupal.org/api/devel/functions/8.x-1.x" rel="noreferrer" target="_blank">https://api.drupal.org/api/<wbr>devel/functions/8.x-1.x</a>><br>
hooks?<br>
<br>
Jason Loeffler<br>
Technology Consultant | The American Academy in Rome<br>
Minor Science | Application Development & Metadata Strategy<br>
Brooklyn, New York<br>
<a href="mailto:jason@minorscience.com">jason@minorscience.com</a><br>
(347) 405-0826<br>
minorscience (Skype)<br>
<br>
<br>
<br>
On Tue, Nov 15, 2016 at 6:17 PM, James Bullen <<a href="mailto:james@hudmol.com">james@hudmol.com</a>> wrote:<br>
<br>
><br>
> Hi all,<br>
><br>
> As part of our new role as ArchivesSpace development partner, we will be<br>
> addressing issues like this as a priority.<br>
><br>
> It is still early days and we?re working with the folks at the<br>
> ArchivesSpace program on a release schedule, so we can?t make any<br>
> definitive statements yet, but please know that we are aware of this issue<br>
> and will address it as soon as we are able.<br>
><br>
><br>
> Cheers,<br>
> James<br>
><br>
><br>
> ?<br>
> James Bullen<br>
> Hudson Molonglo<br>
><br>
><br>
><br>
> On Nov 16, 2016, at 7:46 AM, Joshua D. Shaw <<a href="mailto:Joshua.D.Shaw@dartmouth.edu">Joshua.D.Shaw@dartmouth.edu</a>><br>
> wrote:<br>
><br>
> Hi all ?<br>
><br>
> We at Dartmouth have experienced similar issues. We have some large<br>
> resources as well (one has 60K+ objects in the tree) and anything that<br>
> involves a save or rearrangement (moving a file around, etc) can take a *<br>
> *lot** of time (many minutes) and may cause an error ? typically of the<br>
> ?another user is modifying this record? type.<br>
><br>
> If we have to do any modifications to a resource of that size, we a)<br>
> budget a lot of time and b) do things in small increments ? ie don?t move<br>
> more than a couple of files around at a time. It?s not a great solution,<br>
> but it does minimize some of the headache.<br>
><br>
> I **think** (but haven?t had the time to really dig into this) that one<br>
> reason the error comes about is because the indexer steps on/collides with<br>
> the process that the save/arrangement kicked off. We are still running 1.3<br>
> and hope that some of our issues will be mitigated when we move to 1.5.1,<br>
> though we know that not all of them have been resolved yet.<br>
><br>
> One other data point is that we?ve got a plugin that runs as a background<br>
> job doing a bunch of importing. This background job touches some of the<br>
> larger resources, but does **not** cause the errors and long save times,<br>
> which leads me to believe that a lot of the problem is in the frontend ?<br>
> perhaps with the way the tree is populated - as Jason pointed out.<br>
><br>
> Best,<br>
> Joshua<br>
><br>
> *From: *<<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-<wbr>bounces@lyralists.lyrasis.org</a>> on<br>
> behalf of Jason Loeffler <<a href="mailto:j@minorscience.com">j@minorscience.com</a>><br>
> *Reply-To: *Archivesspace Users Group <archivesspace_users_group@<br>
> <a href="http://lyralists.lyrasis.org" rel="noreferrer" target="_blank">lyralists.lyrasis.org</a>><br>
> *Date: *Tuesday, November 15, 2016 at 3:25 PM<br>
> *To: *Archivesspace Users Group <archivesspace_users_group@<br>
> <a href="http://lyralists.lyrasis.org" rel="noreferrer" target="_blank">lyralists.lyrasis.org</a>><br>
> *Cc: *"<a href="mailto:archivesspace@googlegroups.com">archivesspace@googlegroups.<wbr>com</a>" <<a href="mailto:archivesspace@googlegroups.com">archivesspace@googlegroups.<wbr>com</a>><br>
> *Subject: *Re: [Archivesspace_Users_Group] Problems working with archival<br>
> object with large number of direct children<br>
><br>
> Hi Sally,<br>
><br>
> Definitely, yes. We have many resources with 5,000 or more archival object<br>
> records. We've deployed on some pretty decent Amazon EC2 boxes (16GB<br>
> memory, burstable CPU, etc.) with negligible improvement. I have a feeling<br>
> that this is not a resource allocation issue. Looking at the web inspector,<br>
> most of the time is spent negotiating jstree <<a href="http://jstree.com/" rel="noreferrer" target="_blank">http://jstree.com/</a>> and/or<br>
> loading* all JSON objects* associated with a resource into the browser.<br>
> Maybe an ASpace dev can weigh in.<br>
><br>
><br>
> From the sysadmin side, Maureen Callahan at Yale commissioned Percona to<br>
> evaluate ArchivesSpace and MySQL performance. I've attached the report. Let<br>
> me know if you need any help interpreting the report.<br>
><br>
> At some point, and quite apart from this thread, I hope we can<br>
> collectively revisit the staff interface architecture and recommend<br>
> improvements.<br>
><br>
> JL<br>
><br>
> On Tue, Nov 15, 2016 at 2:37 PM, Sally Vermaaten <<a href="mailto:sally.vermaaten@nyu.edu">sally.vermaaten@nyu.edu</a>><br>
> wrote:<br>
><br>
> Hi everyone,<br>
><br>
> We're running into an issue with a large resource record in ArchivesSpace<br>
> and wonder if anyone has experienced a similar issue. In one resource<br>
> record, we have a series/archival object with around 19,000 direct<br>
> children/archival objects. We've found that:<br>
> ? it takes several minutes to open the series in the 'tree'<br>
> navigation view and then, once opened scrolling through series is very slow<br>
> / laggy<br>
> ? it takes a couple of minutes to open any archival object in the<br>
> series in edit mode and<br>
> ? it takes a couple of minutes to save changes to any archival<br>
> object within the series<br>
> Does anyone else have a similarly large archival object in a resource<br>
> record? If so, have you observed the same long load/save time when editing<br>
> the component records?<br>
><br>
> The slow load time does not seem to be affected by memory allocation;<br>
> we've tried increasing the speed / size of the server and it seemed to have<br>
> no effect. We'd definitely appreciate any other suggestions for how we<br>
> might fix or work around the problem.<br>
><br>
> We also wonder if this performance issue is essentially caused by the<br>
> queries being run to generate the UI view - i.e. perhaps in generating the<br>
> resource 'tree' view, all data for the whole series (all 19k archival<br>
> objects) is being retrieved and stored in memory? If so, we wondered if it<br>
> would be possible and would make sense to change the queries running during<br>
> tree generation, etc. to only retrieve some batches at a time, lazy loading<br>
> style?<br>
><br>
> Thanks,<br>
> Weatherly and Sally<br>
><br>
> --<br>
> Sally Vermaaten<br>
> Project Manager, Archival Systems<br>
> New York University Libraries<br>
> 1-212-992-6259<br>
><br>
><br>
> ______________________________<wbr>_________________<br>
> Archivesspace_Users_Group mailing list<br>
> <a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a><br>
> <a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a><br>
><br>
><br>
> !DSPAM:<wbr>582b7444314351074817778! ______________________________<wbr>_____<br>
> ____________<br>
> Archivesspace_Users_Group mailing list<br>
> <a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a><br>
> <a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a><br>
><br>
><br>
> !DSPAM:<wbr>582b7444314351074817778!<br>
><br>
><br>
><br>
> ______________________________<wbr>_________________<br>
> Archivesspace_Users_Group mailing list<br>
> <a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a><br>
> <a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>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/20161115/129b5b6e/attachment-0001.html" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>pipermail/archivesspace_users_<wbr>group/attachments/20161115/<wbr>129b5b6e/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 17<br>
Date: Wed, 16 Nov 2016 10:56:38 +1100<br>
From: James Bullen <<a href="mailto:james@hudmol.com">james@hudmol.com</a>><br>
To: Archivesspace Users Group<br>
<<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a>><br>
Cc: <a href="mailto:archivesspace@googlegroups.com">archivesspace@googlegroups.com</a><br>
Subject: Re: [Archivesspace_Users_Group] Problems working with<br>
archival object with large number of direct children<br>
Message-ID: <<a href="mailto:E1A76F49-19CF-4743-A5A9-523FDC5DA155@hudmol.com">E1A76F49-19CF-4743-A5A9-<wbr>523FDC5DA155@hudmol.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
<br>
Hi Jason - I?m not aware of a script like this. Cheers ? James<br>
<br>
<br>
> On Nov 16, 2016, at 10:28 AM, Jason Loeffler <<a href="mailto:j@minorscience.com">j@minorscience.com</a>> wrote:<br>
><br>
> Thanks so much, James. Can you tell me if there's a script available for generating an arbitrary number of test records? Something similar to Drupal's devel generate <<a href="https://api.drupal.org/api/devel/functions/8.x-1.x" rel="noreferrer" target="_blank">https://api.drupal.org/api/<wbr>devel/functions/8.x-1.x</a>> hooks?<br>
><br>
> Jason Loeffler<br>
> Technology Consultant | The American Academy in Rome<br>
> Minor Science | Application Development & Metadata Strategy<br>
> Brooklyn, New York<br>
> <a href="mailto:jason@minorscience.com">jason@minorscience.com</a> <mailto:<a href="mailto:jason@minorscience.com">jason@minorscience.com</a><wbr>><br>
> (347) 405-0826<br>
> minorscience (Skype)<br>
><br>
><br>
><br>
> On Tue, Nov 15, 2016 at 6:17 PM, James Bullen <<a href="mailto:james@hudmol.com">james@hudmol.com</a> <mailto:<a href="mailto:james@hudmol.com">james@hudmol.com</a>>> wrote:<br>
><br>
> Hi all,<br>
><br>
> As part of our new role as ArchivesSpace development partner, we will be addressing issues like this as a priority.<br>
><br>
> It is still early days and we?re working with the folks at the ArchivesSpace program on a release schedule, so we can?t make any definitive statements yet, but please know that we are aware of this issue and will address it as soon as we are able.<br>
><br>
><br>
> Cheers,<br>
> James<br>
><br>
><br>
> ?<br>
> James Bullen<br>
> Hudson Molonglo<br>
><br>
><br>
><br>
>> On Nov 16, 2016, at 7:46 AM, Joshua D. Shaw <<a href="mailto:Joshua.D.Shaw@dartmouth.edu">Joshua.D.Shaw@dartmouth.edu</a> <mailto:<a href="mailto:Joshua.D.Shaw@dartmouth.edu">Joshua.D.Shaw@<wbr>dartmouth.edu</a>>> wrote:<br>
>><br>
>> Hi all ?<br>
>><br>
>> We at Dartmouth have experienced similar issues. We have some large resources as well (one has 60K+ objects in the tree) and anything that involves a save or rearrangement (moving a file around, etc) can take a *lot* of time (many minutes) and may cause an error ? typically of the ?another user is modifying this record? type.<br>
>><br>
>> If we have to do any modifications to a resource of that size, we a) budget a lot of time and b) do things in small increments ? ie don?t move more than a couple of files around at a time. It?s not a great solution, but it does minimize some of the headache.<br>
>><br>
>> I *think* (but haven?t had the time to really dig into this) that one reason the error comes about is because the indexer steps on/collides with the process that the save/arrangement kicked off. We are still running 1.3 and hope that some of our issues will be mitigated when we move to 1.5.1, though we know that not all of them have been resolved yet.<br>
>><br>
>> One other data point is that we?ve got a plugin that runs as a background job doing a bunch of importing. This background job touches some of the larger resources, but does *not* cause the errors and long save times, which leads me to believe that a lot of the problem is in the frontend ? perhaps with the way the tree is populated - as Jason pointed out.<br>
>><br>
>> Best,<br>
>> Joshua<br>
>><br>
>> From: <<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-<wbr>bounces@lyralists.lyrasis.org</a> <mailto:<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_<wbr>group-bounces@lyralists.<wbr>lyrasis.org</a>>> on behalf of Jason Loeffler <<a href="mailto:j@minorscience.com">j@minorscience.com</a> <mailto:<a href="mailto:j@minorscience.com">j@minorscience.com</a>>><br>
>> Reply-To: Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a> <mailto:<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_<wbr>group@lyralists.lyrasis.org</a>>><br>
>> Date: Tuesday, November 15, 2016 at 3:25 PM<br>
>> To: Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a> <mailto:<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_<wbr>group@lyralists.lyrasis.org</a>>><br>
>> Cc: "<a href="mailto:archivesspace@googlegroups.com">archivesspace@googlegroups.<wbr>com</a> <mailto:<a href="mailto:archivesspace@googlegroups.com">archivesspace@<wbr>googlegroups.com</a>>" <<a href="mailto:archivesspace@googlegroups.com">archivesspace@googlegroups.<wbr>com</a> <mailto:<a href="mailto:archivesspace@googlegroups.com">archivesspace@<wbr>googlegroups.com</a>>><br>
>> Subject: Re: [Archivesspace_Users_Group] Problems working with archival object with large number of direct children<br>
>><br>
>> Hi Sally,<br>
>><br>
>> Definitely, yes. We have many resources with 5,000 or more archival object records. We've deployed on some pretty decent Amazon EC2 boxes (16GB memory, burstable CPU, etc.) with negligible improvement. I have a feeling that this is not a resource allocation issue. Looking at the web inspector, most of the time is spent negotiating jstree <<a href="http://jstree.com/" rel="noreferrer" target="_blank">http://jstree.com/</a>> and/or loading all JSON objects associated with a resource into the browser. Maybe an ASpace dev can weigh in.<br>
>><br>
>><br>
>> From the sysadmin side, Maureen Callahan at Yale commissioned Percona to evaluate ArchivesSpace and MySQL performance. I've attached the report. Let me know if you need any help interpreting the report.<br>
>><br>
>> At some point, and quite apart from this thread, I hope we can collectively revisit the staff interface architecture and recommend improvements.<br>
>><br>
>> JL<br>
>><br>
>> On Tue, Nov 15, 2016 at 2:37 PM, Sally Vermaaten <<a href="mailto:sally.vermaaten@nyu.edu">sally.vermaaten@nyu.edu</a> <mailto:<a href="mailto:sally.vermaaten@nyu.edu">sally.vermaaten@nyu.<wbr>edu</a>>> wrote:<br>
>>> Hi everyone,<br>
>>><br>
>>> We're running into an issue with a large resource record in ArchivesSpace and wonder if anyone has experienced a similar issue. In one resource record, we have a series/archival object with around 19,000 direct children/archival objects. We've found that:<br>
>>> ? it takes several minutes to open the series in the 'tree' navigation view and then, once opened scrolling through series is very slow / laggy<br>
>>> ? it takes a couple of minutes to open any archival object in the series in edit mode and<br>
>>> ? it takes a couple of minutes to save changes to any archival object within the series<br>
>>> Does anyone else have a similarly large archival object in a resource record? If so, have you observed the same long load/save time when editing the component records?<br>
>>><br>
>>> The slow load time does not seem to be affected by memory allocation; we've tried increasing the speed / size of the server and it seemed to have no effect. We'd definitely appreciate any other suggestions for how we might fix or work around the problem.<br>
>>><br>
>>> We also wonder if this performance issue is essentially caused by the queries being run to generate the UI view - i.e. perhaps in generating the resource 'tree' view, all data for the whole series (all 19k archival objects) is being retrieved and stored in memory? If so, we wondered if it would be possible and would make sense to change the queries running during tree generation, etc. to only retrieve some batches at a time, lazy loading style?<br>
>>><br>
>>> Thanks,<br>
>>> Weatherly and Sally<br>
>>><br>
>>> --<br>
>>> Sally Vermaaten<br>
>>> Project Manager, Archival Systems<br>
>>> New York University Libraries<br>
>>> 1-212-992-6259 <tel:1-212-992-6259><br>
>>><br>
>>> ______________________________<wbr>_________________<br>
>>> Archivesspace_Users_Group mailing list<br>
>>> <a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a> <mailto:<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_<wbr>Group@lyralists.lyrasis.org</a>><br>
>>> <a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a> <<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a>><br>
>><br>
>> wbr>582b7444314351074817778! ______________________________<wbr>_________________<br>
>> Archivesspace_Users_Group mailing list<br>
>> <a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a> <mailto:<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_<wbr>Group@lyralists.lyrasis.org</a>><br>
>> <a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a> <<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a>><br>
>><br>
>><br>
>> !DSPAM:<wbr>582b7444314351074817778!<br>
><br>
><br>
> ______________________________<wbr>_________________<br>
> Archivesspace_Users_Group mailing list<br>
> <a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a> <mailto:<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_<wbr>Group@lyralists.lyrasis.org</a>><br>
> <a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a> <<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a>><br>
><br>
><br>
> !DSPAM:<wbr>582b9a4b138833087816299! ______________________________<wbr>_________________<br>
> Archivesspace_Users_Group mailing list<br>
> <a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a> <mailto:<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_<wbr>Group@lyralists.lyrasis.org</a>><br>
> <a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a> <<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a>><br>
><br>
><br>
> !DSPAM:<wbr>582b9a4b138833087816299!<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20161116/7b414b69/attachment-0001.html" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>pipermail/archivesspace_users_<wbr>group/attachments/20161116/<wbr>7b414b69/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 18<br>
Date: Wed, 16 Nov 2016 00:47:14 +0000<br>
From: "Gadsby, Eric T." <<a href="mailto:egadsby@towson.edu">egadsby@towson.edu</a>><br>
To: "<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a>"<br>
<<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a>><br>
Subject: [Archivesspace_Users_Group] A user who is set as manager of a<br>
collection can not create containers...<br>
Message-ID: <<a href="mailto:52B9DEC3-08BD-43F0-ABCC-0DA6A4AB4BA4@towson.edu">52B9DEC3-08BD-43F0-ABCC-<wbr>0DA6A4AB4BA4@towson.edu</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
I posted this to the list earlier but the list seems more active this week so I thought I?d try again. One of ouse users is manger of a collection but can?t create containers in it here is what they report:<br>
<br>
?While attempting to create top containers for instances, I only had access to ?browse? but not create. I had management level access at the time. I had to be given admin level access to be able to gain the create button for top containers. The create option disappeared when placed on just admin level access. I had to be placed in both levels of access to be able to create top containers.?<br>
<br>
Our server has only been in production for a few weeks and is set-up per the <a href="http://www.archivesspace.org" rel="noreferrer" target="_blank">http://www.archivesspace.org</a> recommendations. Our server does authenticate via LDAP (Active Directory) but our users experience is the same using an AD or ArchivesSpace local users. Do you know how we might resolve this or what might be the next steps in troubleshooting? Thanks!<br>
<br>
Sincerely,<br>
<br>
Eric T Gadsby<br>
IT Operations Specialist, Cook Library<br>
Towson University<br>
<a href="mailto:egadsby@towson.edu">egadsby@towson.edu</a><mailto:<a href="mailto:egadsby@towson.edu">egad<wbr>sby@towson.edu</a>><br>
410-704-3340<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20161116/2170c700/attachment-0001.html" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>pipermail/archivesspace_users_<wbr>group/attachments/20161116/<wbr>2170c700/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 19<br>
Date: Wed, 16 Nov 2016 02:10:52 +0000 (UTC)<br>
From: Jason Loeffler <<a href="mailto:j@minorscience.com">j@minorscience.com</a>><br>
To: Archivesspace Users Group<br>
<<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a>><br>
Cc: <a href="mailto:archivesspace@googlegroups.com">archivesspace@googlegroups.com</a><br>
Subject: Re: [Archivesspace_Users_Group] Problems working with<br>
archival object with large number of direct children<br>
Message-ID:<br>
<<a href="mailto:E0903B9C708FD3BF.5EEE58AA-F43D-496F-AA20-9F8755C27EEE@mail.outlook.com">E0903B9C708FD3BF.5EEE58AA-<wbr>F43D-496F-AA20-9F8755C27EEE@<wbr>mail.outlook.com</a>><br>
<br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
<br>
Thanks, James. Just wondering if there's a load test battery for a large dataset. I can generate a large dataset if you think it is useful for your work.?<br>
<br>
<br>
<br>
<br>
On Tue, Nov 15, 2016 at 6:56 PM -0500, "James Bullen" <<a href="mailto:james@hudmol.com">james@hudmol.com</a>> wrote:<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
Hi Jason - I?m not aware of a script like this. ?Cheers ? James<br>
<br>
On Nov 16, 2016, at 10:28 AM, Jason Loeffler <<a href="mailto:j@minorscience.com">j@minorscience.com</a>> wrote:<br>
Thanks so much, James. Can you tell me if there's a script available for generating an arbitrary number of test records? Something similar to Drupal's devel?generate?hooks?<br>
Jason LoefflerTechnology Consultant |?The American Academy in RomeMinor Science | Application Development & Metadata StrategyBrooklyn, New <a href="mailto:Yorkjason@minorscience.com">Yorkjason@minorscience.com</a>(<wbr>347) 405-0826minorscience (Skype)<br>
<br>
<br>
On Tue, Nov 15, 2016 at 6:17 PM, James Bullen?<<a href="mailto:james@hudmol.com">james@hudmol.com</a>>?<wbr>wrote:<br>
<br>
Hi all,<br>
As part of our new role as ArchivesSpace development partner, we will be addressing issues like this as a priority.<br>
It is still early days and we?re working with the folks at the ArchivesSpace program on a release schedule, so we can?t make any definitive statements yet, but please know that we are aware of this issue and will address it as soon as we are able.<br>
<br>
Cheers,James<br>
<br>
?James BullenHudson Molonglo<br>
<br>
<br>
On Nov 16, 2016, at 7:46 AM, Joshua D. Shaw <<a href="mailto:Joshua.D.Shaw@dartmouth.edu">Joshua.D.Shaw@dartmouth.edu</a>> wrote:<br>
Hi all ??We at Dartmouth have experienced similar issues. We have some large resources as well (one has 60K+ objects in the tree) and anything that involves a save or rearrangement (moving a file around, etc) can take a *lot* of time (many minutes) and may cause an error ? typically of the ?another user is modifying this record? type.?If we have to do any modifications to a resource of that size, we a) budget a lot of time and b) do things in small increments ? ie don?t move more than a couple of files around at a time. It?s not a great solution, but it does minimize some of the headache.?I *think* (but haven?t had the time to really dig into this) that one reason the error comes about is because the indexer steps on/collides with the process that the save/arrangement kicked off. We are still running 1.3 and hope that some of our issues will be mitigated when we move to 1.5.1, though we know that not all of them have been resolved yet.?One other data point is that we?ve got !<br>
a plugin<br>
that runs as a background job doing a bunch of importing. This background job touches some of the larger resources, but does *not* cause the errors and long save times, which leads me to believe that a lot of the problem is in the frontend ? perhaps with the way the tree is populated - as Jason pointed out.?Best,Joshua?From:?<<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archiv<wbr>esspace_users_group-bounces@<wbr>lyralists.lyrasis.org</a>> on behalf of Jason Loeffler <<a href="mailto:j@minorscience.com">j@minorscience.com</a>><br>
Reply-To:?Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a>><br>
Date:?Tuesday, November 15, 2016 at 3:25 PM<br>
To:?Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a>><br>
Cc:?"<a href="mailto:archivesspace@googlegroups.com">archivesspace@<wbr>googlegroups.com</a>" <<a href="mailto:archivesspace@googlegroups.com">archivesspace@googlegroups.<wbr>com</a>><br>
Subject:?Re: [Archivesspace_Users_Group] Problems working with archival object with large number of direct children?Hi Sally,?Definitely, yes. We have many resources with 5,000 or more archival object records. We've deployed on some pretty decent Amazon EC2 boxes (16GB memory, burstable CPU, etc.) with negligible improvement. I have a feeling that this is not a resource allocation issue. Looking at the web inspector, most of the time is spent negotiating?jstree?and/or loading?all JSON objects?associated with a resource into the browser. Maybe an ASpace dev can weigh in.<br>
<br>
>From the sysadmin side, Maureen Callahan at Yale commissioned Percona to evaluate ArchivesSpace and MySQL performance. I've attached the report. Let me know if you need any help interpreting the report.?At some point, and quite apart from this thread, I hope we can collectively revisit the staff interface architecture and recommend improvements.??JL?On Tue, Nov 15, 2016 at 2:37 PM, Sally Vermaaten <<a href="mailto:sally.vermaaten@nyu.edu">sally.vermaaten@nyu.edu</a>> wrote:Hi everyone,?We're running into an issue with a large resource record in ArchivesSpace and wonder if anyone has experienced a similar issue.?In one resource record, we have a series/archival object with around 19,000 direct children/archival objects. We've found that: ???????????it takes several minutes to open the series in the 'tree' navigation view and then, once opened scrolling through series is very slow / laggy??????????it takes a couple of minutes to open any archival object in the series in edit mode and???????????it takes a couple of minut!<br>
es to sav<br>
e changes to any archival object within the seriesDoes anyone else have a similarly large archival object in a resource record? If so, have you observed the same long load/save time when editing the component records???The slow load time does not seem to be affected by memory allocation; we've tried increasing the speed / size of the server and it seemed to have no effect. We'd definitely appreciate any other suggestions for how we might fix or work around the problem.?We also wonder if this performance issue is essentially caused by the queries being run to generate the UI view - i.e. perhaps in generating the resource 'tree' view, all data for the whole series (all 19k archival objects) is being retrieved and stored in memory? If so, we wondered if it would be possible and would make sense to change the queries running during tree generation, etc. to only retrieve some batches at a time, lazy loading style???Thanks,Weatherly?and Sally?--?Sally Vermaaten<br>
Project Manager, Archival Systems<br>
New York University Libraries1-212-992-6259<br>
<br>
<br>
______________________________<wbr>_________________<br>
Archivesspace_Users_Group mailing list<br>
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a><br>
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group?wbr" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group?wbr</a>><wbr>582b7444314351074817778!?_____<wbr>______________________________<wbr>____________<br>
Archivesspace_Users_Group mailing list<br>
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a><br>
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a><br>
<br>
<br>
!DSPAM:<wbr>582b7444314351074817778!<br>
<br>
<br>
______________________________<wbr>_________________<br>
Archivesspace_Users_Group mailing list<br>
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a><br>
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a><br>
<br>
<br>
!DSPAM:<wbr>582b9a4b138833087816299! ______________________________<wbr>_________________<br>
Archivesspace_Users_Group mailing list<br>
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a><br>
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a><br>
<br>
<br>
!DSPAM:<wbr>582b9a4b138833087816299!<br>
<br>
<br>
<br>
<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20161116/272967ce/attachment-0001.html" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>pipermail/archivesspace_users_<wbr>group/attachments/20161116/<wbr>272967ce/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 20<br>
Date: Wed, 16 Nov 2016 13:34:17 +1100<br>
From: James Bullen <<a href="mailto:james@hudmol.com">james@hudmol.com</a>><br>
To: Archivesspace Users Group<br>
<<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a>><br>
Cc: <a href="mailto:archivesspace@googlegroups.com">archivesspace@googlegroups.com</a><br>
Subject: Re: [Archivesspace_Users_Group] Problems working with<br>
archival object with large number of direct children<br>
Message-ID: <<a href="mailto:6C7D60FD-2AA6-447C-A55A-19BCC2433E49@hudmol.com">6C7D60FD-2AA6-447C-A55A-<wbr>19BCC2433E49@hudmol.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
<br>
That could be useful thanks Jason. Cheers ? James<br>
<br>
<br>
> On Nov 16, 2016, at 1:10 PM, Jason Loeffler <<a href="mailto:j@minorscience.com">j@minorscience.com</a>> wrote:<br>
><br>
><br>
> Thanks, James. Just wondering if there's a load test battery for a large dataset. I can generate a large dataset if you think it is useful for your work.<br>
><br>
><br>
><br>
><br>
> On Tue, Nov 15, 2016 at 6:56 PM -0500, "James Bullen" <<a href="mailto:james@hudmol.com">james@hudmol.com</a> <mailto:<a href="mailto:james@hudmol.com">james@hudmol.com</a>>> wrote:<br>
><br>
><br>
> Hi Jason - I?m not aware of a script like this. Cheers ? James<br>
><br>
><br>
>> On Nov 16, 2016, at 10:28 AM, Jason Loeffler <<a href="mailto:j@minorscience.com">j@minorscience.com</a> <mailto:<a href="mailto:j@minorscience.com">j@minorscience.com</a>>> wrote:<br>
>><br>
>> Thanks so much, James. Can you tell me if there's a script available for generating an arbitrary number of test records? Something similar to Drupal's devel generate <<a href="https://api.drupal.org/api/devel/functions/8.x-1.x" rel="noreferrer" target="_blank">https://api.drupal.org/api/<wbr>devel/functions/8.x-1.x</a>> hooks?<br>
>><br>
>> Jason Loeffler<br>
>> Technology Consultant | The American Academy in Rome<br>
>> Minor Science | Application Development & Metadata Strategy<br>
>> Brooklyn, New York<br>
>> <a href="mailto:jason@minorscience.com">jason@minorscience.com</a> <mailto:<a href="mailto:jason@minorscience.com">jason@minorscience.com</a><wbr>><br>
>> (347) 405-0826<br>
>> minorscience (Skype)<br>
>><br>
>><br>
>><br>
>> On Tue, Nov 15, 2016 at 6:17 PM, James Bullen <<a href="mailto:james@hudmol.com">james@hudmol.com</a> <mailto:<a href="mailto:james@hudmol.com">james@hudmol.com</a>>> wrote:<br>
>><br>
>> Hi all,<br>
>><br>
>> As part of our new role as ArchivesSpace development partner, we will be addressing issues like this as a priority.<br>
>><br>
>> It is still early days and we?re working with the folks at the ArchivesSpace program on a release schedule, so we can?t make any definitive statements yet, but please know that we are aware of this issue and will address it as soon as we are able.<br>
>><br>
>><br>
>> Cheers,<br>
>> James<br>
>><br>
>><br>
>> ?<br>
>> James Bullen<br>
>> Hudson Molonglo<br>
>><br>
>><br>
>><br>
>>> On Nov 16, 2016, at 7:46 AM, Joshua D. Shaw <<a href="mailto:Joshua.D.Shaw@dartmouth.edu">Joshua.D.Shaw@dartmouth.edu</a> <mailto:<a href="mailto:Joshua.D.Shaw@dartmouth.edu">Joshua.D.Shaw@<wbr>dartmouth.edu</a>>> wrote:<br>
>>><br>
>>> Hi all ?<br>
>>><br>
>>> We at Dartmouth have experienced similar issues. We have some large resources as well (one has 60K+ objects in the tree) and anything that involves a save or rearrangement (moving a file around, etc) can take a *lot* of time (many minutes) and may cause an error ? typically of the ?another user is modifying this record? type.<br>
>>><br>
>>> If we have to do any modifications to a resource of that size, we a) budget a lot of time and b) do things in small increments ? ie don?t move more than a couple of files around at a time. It?s not a great solution, but it does minimize some of the headache.<br>
>>><br>
>>> I *think* (but haven?t had the time to really dig into this) that one reason the error comes about is because the indexer steps on/collides with the process that the save/arrangement kicked off. We are still running 1.3 and hope that some of our issues will be mitigated when we move to 1.5.1, though we know that not all of them have been resolved yet.<br>
>>><br>
>>> One other data point is that we?ve got a plugin that runs as a background job doing a bunch of importing. This background job touches some of the larger resources, but does *not* cause the errors and long save times, which leads me to believe that a lot of the problem is in the frontend ? perhaps with the way the tree is populated - as Jason pointed out.<br>
>>><br>
>>> Best,<br>
>>> Joshua<br>
>>><br>
>>> From: <<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-<wbr>bounces@lyralists.lyrasis.org</a> <mailto:<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_<wbr>group-bounces@lyralists.<wbr>lyrasis.org</a>>> on behalf of Jason Loeffler <<a href="mailto:j@minorscience.com">j@minorscience.com</a> <mailto:<a href="mailto:j@minorscience.com">j@minorscience.com</a>>><br>
>>> Reply-To: Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a> <mailto:<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_<wbr>group@lyralists.lyrasis.org</a>>><br>
>>> Date: Tuesday, November 15, 2016 at 3:25 PM<br>
>>> To: Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a> <mailto:<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_<wbr>group@lyralists.lyrasis.org</a>>><br>
>>> Cc: "<a href="mailto:archivesspace@googlegroups.com">archivesspace@googlegroups.<wbr>com</a> <mailto:<a href="mailto:archivesspace@googlegroups.com">archivesspace@<wbr>googlegroups.com</a>>" <<a href="mailto:archivesspace@googlegroups.com">archivesspace@googlegroups.<wbr>com</a> <mailto:<a href="mailto:archivesspace@googlegroups.com">archivesspace@<wbr>googlegroups.com</a>>><br>
>>> Subject: Re: [Archivesspace_Users_Group] Problems working with archival object with large number of direct children<br>
>>><br>
>>> Hi Sally,<br>
>>><br>
>>> Definitely, yes. We have many resources with 5,000 or more archival object records. We've deployed on some pretty decent Amazon EC2 boxes (16GB memory, burstable CPU, etc.) with negligible improvement. I have a feeling that this is not a resource allocation issue. Looking at the web inspector, most of the time is spent negotiating jstree <<a href="http://jstree.com/" rel="noreferrer" target="_blank">http://jstree.com/</a>> and/or loading all JSON objects associated with a resource into the browser. Maybe an ASpace dev can weigh in.<br>
>>><br>
>>><br>
>>> From the sysadmin side, Maureen Callahan at Yale commissioned Percona to evaluate ArchivesSpace and MySQL performance. I've attached the report. Let me know if you need any help interpreting the report.<br>
>>><br>
>>> At some point, and quite apart from this thread, I hope we can collectively revisit the staff interface architecture and recommend improvements.<br>
>>><br>
>>> JL<br>
>>><br>
>>> On Tue, Nov 15, 2016 at 2:37 PM, Sally Vermaaten <<a href="mailto:sally.vermaaten@nyu.edu">sally.vermaaten@nyu.edu</a> <mailto:<a href="mailto:sally.vermaaten@nyu.edu">sally.vermaaten@nyu.<wbr>edu</a>>> wrote:<br>
>>>> Hi everyone,<br>
>>>><br>
>>>> We're running into an issue with a large resource record in ArchivesSpace and wonder if anyone has experienced a similar issue. In one resource record, we have a series/archival object with around 19,000 direct children/archival objects. We've found that:<br>
>>>> ? it takes several minutes to open the series in the 'tree' navigation view and then, once opened scrolling through series is very slow / laggy<br>
>>>> ? it takes a couple of minutes to open any archival object in the series in edit mode and<br>
>>>> ? it takes a couple of minutes to save changes to any archival object within the series<br>
>>>> Does anyone else have a similarly large archival object in a resource record? If so, have you observed the same long load/save time when editing the component records?<br>
>>>><br>
>>>> The slow load time does not seem to be affected by memory allocation; we've tried increasing the speed / size of the server and it seemed to have no effect. We'd definitely appreciate any other suggestions for how we might fix or work around the problem.<br>
>>>><br>
>>>> We also wonder if this performance issue is essentially caused by the queries being run to generate the UI view - i.e. perhaps in generating the resource 'tree' view, all data for the whole series (all 19k archival objects) is being retrieved and stored in memory? If so, we wondered if it would be possible and would make sense to change the queries running during tree generation, etc. to only retrieve some batches at a time, lazy loading style?<br>
>>>><br>
>>>> Thanks,<br>
>>>> Weatherly and Sally<br>
>>>><br>
>>>> --<br>
>>>> Sally Vermaaten<br>
>>>> Project Manager, Archival Systems<br>
>>>> New York University Libraries<br>
>>>> 1-212-992-6259 <tel:1-212-992-6259><br>
>>>><br>
>>>> ______________________________<wbr>_________________<br>
>>>> Archivesspace_Users_Group mailing list<br>
>>>> <a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a> <mailto:<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_<wbr>Group@lyralists.lyrasis.org</a>><br>
>>>> <a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a> <<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a>><br>
>>><br>
>>> wbr>582b7444314351074817778! ______________________________<wbr>_________________<br>
>>> Archivesspace_Users_Group mailing list<br>
>>> <a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a> <mailto:<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_<wbr>Group@lyralists.lyrasis.org</a>><br>
>>> <a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a> <<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a>><br>
>>><br>
>>><br>
>>> wbr class=""><wbr>582b7444314351074817778!<br>
>><br>
>><br>
>> ______________________________<wbr>_________________<br>
>> Archivesspace_Users_Group mailing list<br>
>> <a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a> <mailto:<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_<wbr>Group@lyralists.lyrasis.org</a>><br>
>> <a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a> <<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a>><br>
>><br>
>><br>
>> !DSPAM:<wbr>582b9a4b138833087816299! ______________________________<wbr>_________________<br>
>> Archivesspace_Users_Group mailing list<br>
>> <a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a> <mailto:<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_<wbr>Group@lyralists.lyrasis.org</a>><br>
>> <a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a> <<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a>><br>
>><br>
>><br>
>> !DSPAM:<wbr>582b9a4b138833087816299!<br>
><br>
> !DSPAM:<wbr>582bc03b277649809715286!<br>
> ______________________________<wbr>_________________<br>
> Archivesspace_Users_Group mailing list<br>
> <a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a><br>
> <a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a><br>
><br>
><br>
> !DSPAM:<wbr>582bc03b277649809715286!<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20161116/da104852/attachment-0001.html" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>pipermail/archivesspace_users_<wbr>group/attachments/20161116/<wbr>da104852/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 21<br>
Date: Wed, 16 Nov 2016 18:20:26 +1100<br>
From: Payten Giles <<a href="mailto:payten@paytengiles.com">payten@paytengiles.com</a>><br>
To: Archivesspace Users Group<br>
<<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a>><br>
Subject: Re: [Archivesspace_Users_Group] A user who is set as manager<br>
of a collection can not create containers...<br>
Message-ID: <<a href="mailto:etPan.582c08d8.50b81168.1fc@paytengiles.com">etPan.582c08d8.50b81168.1fc@<wbr>paytengiles.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi there Eric,<br>
<br>
Access to the ?Create? for containers is provided by the?update_container_record role. ?It looks like this isn?t granted to managers (repository-managers) by default. ?This has a bug vibe and I?ll ensure a JIRA issue is recorded.<br>
<br>
In the meantime, you can expand the roles available to your repository managers by following these steps:<br>
<br>
1. Login as an administrator<br>
2. Ensure the repository you?d like to update is selected<br>
3. Under the ?cog? icon next to the repository name, select "Manage Groups?<br>
4. Select ?Edit? next to the?repository-managers group<br>
5. Under ?Members can?, ensure the checkbox for "create/update top container records? is selected<br>
6. Save Group<br>
<br>
Hopefully the ?Create? action will now be available!<br>
<br>
Thanks,<br>
Payten<br>
<br>
<br>
On 16 November 2016 at 11:47:21 AM, Gadsby, Eric T. (<a href="mailto:egadsby@towson.edu">egadsby@towson.edu</a>) wrote:<br>
<br>
I posted this to the list earlier but the list seems more active this week so I thought I?d try again. One of ouse users is manger of a collection but can?t create containers in it here is what they report:?<br>
<br>
?While attempting to create top containers for instances, I only had access to ?browse? but not create. I had management level access at the time. I had to be given admin level access to be able to gain the create button for top containers. The create option disappeared when placed on just admin level access. I had to be placed in both levels of access to be able to create top containers.??<br>
<br>
Our server has only been in production for a few weeks and is set-up per the?<a href="http://www.archivesspace.org?recommendations" rel="noreferrer" target="_blank">http://www.archivesspace.<wbr>org?recommendations</a>. Our server does authenticate via LDAP (Active Directory) but our users experience is the same using an AD or ArchivesSpace local users. Do you know how we might resolve this or what might be the next steps in troubleshooting? Thanks!?<br>
<br>
Sincerely,<br>
<br>
Eric T Gadsby<br>
IT Operations Specialist, Cook Library<br>
Towson University<br>
<a href="mailto:egadsby@towson.edu">egadsby@towson.edu</a><br>
410-704-3340 ______________________________<wbr>_________________<br>
Archivesspace_Users_Group mailing list<br>
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a><br>
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20161116/21a11577/attachment-0001.html" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>pipermail/archivesspace_users_<wbr>group/attachments/20161116/<wbr>21a11577/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 22<br>
Date: Wed, 16 Nov 2016 04:05:24 -0300<br>
From: Payten Giles <<a href="mailto:payten.giles@gmail.com">payten.giles@gmail.com</a>><br>
To: Archivesspace Users Group<br>
<<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a>><br>
Subject: Re: [Archivesspace_Users_Group] A user who is set as manager<br>
of a collection can not create containers...<br>
Message-ID:<br>
<CAFwQ+jR8UXQ=pjX=<wbr>itikO8uLe3Nb8NjXwuT=<a href="mailto:N_p4m5ib8q7h0Q@mail.gmail.com">N_<wbr>p4m5ib8q7h0Q@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi there Eric,<br>
<br>
Access to the ?Create? for containers is provided by<br>
the update_container_record role. It looks like this isn?t granted to<br>
managers (repository-managers) by default. This has a bug vibe and I?ll<br>
ensure a JIRA issue is recorded.<br>
<br>
In the meantime, you can expand the roles available to your repository<br>
managers by following these steps:<br>
<br>
1. Login as an administrator<br>
2. Ensure the repository you?d like to update is selected<br>
3. Under the ?cog? icon next to the repository name, select "Manage Groups?<br>
4. Select ?Edit? next to the repository-managers group<br>
5. Under ?Members can?, ensure the checkbox for "create/update top<br>
container records? is selected<br>
6. Save Group<br>
<br>
Hopefully the ?Create? action will now be available!<br>
<br>
Thanks,<br>
Payten<br>
<br>
<br>
On 16 November 2016 at 11:47:21 AM, Gadsby, Eric T. (<a href="mailto:egadsby@towson.edu">egadsby@towson.edu</a>)<br>
wrote:<br>
<br>
I posted this to the list earlier but the list seems more active this week<br>
so I thought I?d try again. One of ouse users is manger of a collection but<br>
can?t create containers in it here is what they report:<br>
<br>
?While attempting to create top containers for instances, I only had access<br>
to ?browse? but not create. I had management level access at the time. I<br>
had to be given admin level access to be able to gain the create button for<br>
top containers. The create option disappeared when placed on just admin<br>
level access. I had to be placed in both levels of access to be able to<br>
create top containers.?<br>
<br>
Our server has only been in production for a few weeks and is set-up per<br>
the <a href="http://www.archivesspace.org" rel="noreferrer" target="_blank">http://www.archivesspace.org</a> recommendations. Our server does<br>
authenticate via LDAP (Active Directory) but our users experience is the<br>
same using an AD or ArchivesSpace local users. Do you know how we might<br>
resolve this or what might be the next steps in troubleshooting? Thanks!<br>
<br>
Sincerely,<br>
<br>
Eric T Gadsby<br>
IT Operations Specialist, Cook Library<br>
Towson University<br>
<a href="mailto:egadsby@towson.edu">egadsby@towson.edu</a><br>
410-704-3340 ______________________________<wbr>_________________<br>
Archivesspace_Users_Group mailing list<br>
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a><br>
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20161116/f0e12ee0/attachment-0001.html" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>pipermail/archivesspace_users_<wbr>group/attachments/20161116/<wbr>f0e12ee0/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 23<br>
Date: Wed, 16 Nov 2016 12:32:22 +0000<br>
From: "Gadsby, Eric T." <<a href="mailto:egadsby@towson.edu">egadsby@towson.edu</a>><br>
To: Archivesspace Users Group<br>
<<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a>><br>
Subject: Re: [Archivesspace_Users_Group] A user who is set as manager<br>
of a collection can not create containers...<br>
Message-ID: <<a href="mailto:BF16D65B-B14C-4FA1-9201-01E90D88934A@towson.edu">BF16D65B-B14C-4FA1-9201-<wbr>01E90D88934A@towson.edu</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Payten,<br>
<br>
Thanks I will have the users try that and report back. Thanks for your help!<br>
<br>
Sincerely,<br>
<br>
Eric T Gadsby<br>
IT Operations Specialist, Cook Library<br>
Towson University<br>
<a href="mailto:egadsby@towson.edu">egadsby@towson.edu</a><mailto:<a href="mailto:egadsby@towson.edu">egad<wbr>sby@towson.edu</a>><br>
410-704-3340<br>
<br>
On Nov 16, 2016, at 2:20 AM, Payten Giles <<a href="mailto:payten@paytengiles.com">payten@paytengiles.com</a><<wbr>mailto:<a href="mailto:payten@paytengiles.com">payten@paytengiles.com</a>><wbr>> wrote:<br>
<br>
Hi there Eric,<br>
<br>
Access to the ?Create? for containers is provided by the update_container_record role. It looks like this isn?t granted to managers (repository-managers) by default. This has a bug vibe and I?ll ensure a JIRA issue is recorded.<br>
<br>
In the meantime, you can expand the roles available to your repository managers by following these steps:<br>
<br>
1. Login as an administrator<br>
2. Ensure the repository you?d like to update is selected<br>
3. Under the ?cog? icon next to the repository name, select "Manage Groups?<br>
4. Select ?Edit? next to the repository-managers group<br>
5. Under ?Members can?, ensure the checkbox for "create/update top container records? is selected<br>
6. Save Group<br>
<br>
Hopefully the ?Create? action will now be available!<br>
<br>
Thanks,<br>
Payten<br>
<br>
<br>
<br>
On 16 November 2016 at 11:47:21 AM, Gadsby, Eric T. (<a href="mailto:egadsby@towson.edu">egadsby@towson.edu</a><mailto:<a href="mailto:egadsby@towson.edu">ega<wbr>dsby@towson.edu</a>>) wrote:<br>
<br>
I posted this to the list earlier but the list seems more active this week so I thought I?d try again. One of ouse users is manger of a collection but can?t create containers in it here is what they report:<br>
<br>
?While attempting to create top containers for instances, I only had access to ?browse? but not create. I had management level access at the time. I had to be given admin level access to be able to gain the create button for top containers. The create option disappeared when placed on just admin level access. I had to be placed in both levels of access to be able to create top containers.?<br>
<br>
Our server has only been in production for a few weeks and is set-up per the <a href="http://www.archivesspace.org" rel="noreferrer" target="_blank">http://www.archivesspace.org</a><<a href="http://www.archivesspace.org/" rel="noreferrer" target="_blank">h<wbr>ttp://www.archivesspace.org/</a>> recommendations. Our server does authenticate via LDAP (Active Directory) but our users experience is the same using an AD or ArchivesSpace local users. Do you know how we might resolve this or what might be the next steps in troubleshooting? Thanks!<br>
<br>
Sincerely,<br>
<br>
Eric T Gadsby<br>
IT Operations Specialist, Cook Library<br>
Towson University<br>
<a href="mailto:egadsby@towson.edu">egadsby@towson.edu</a><mailto:<a href="mailto:egadsby@towson.edu">egad<wbr>sby@towson.edu</a>><br>
410-704-3340 ______________________________<wbr>_________________<br>
Archivesspace_Users_Group mailing list<br>
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a><mailto:<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">A<wbr>rchivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a>><br>
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a><br>
______________________________<wbr>_________________<br>
Archivesspace_Users_Group mailing list<br>
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a><mailto:<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">A<wbr>rchivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a>><br>
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a><br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20161116/2077c8ae/attachment-0001.html" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>pipermail/archivesspace_users_<wbr>group/attachments/20161116/<wbr>2077c8ae/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 24<br>
Date: Wed, 16 Nov 2016 12:45:33 +0000<br>
From: "Joshua D. Shaw" <<a href="mailto:Joshua.D.Shaw@dartmouth.edu">Joshua.D.Shaw@dartmouth.edu</a>><br>
To: Archivesspace Users Group<br>
<<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a>><br>
Subject: Re: [Archivesspace_Users_Group] Problems working with<br>
archival object with large number of direct children<br>
Message-ID: <<a href="mailto:F590EE90-5FE4-45CE-B225-409D33546282@dartmouth.edu">F590EE90-5FE4-45CE-B225-<wbr>409D33546282@dartmouth.edu</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Thanks, James!<br>
<br>
For the rest of the list, especially those who haven?t had a chance to work with James and the rest of the gang at HM, we?ve had nothing but great work on the customizations we?ve had done. All by way of saying that if James says they are gonna fix it? it?ll be fixed!<br>
<br>
Joshua<br>
<br>
From: <<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-<wbr>bounces@lyralists.lyrasis.org</a>> on behalf of James Bullen <<a href="mailto:james@hudmol.com">james@hudmol.com</a>><br>
Reply-To: Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a>><br>
Date: Tuesday, November 15, 2016 at 6:17 PM<br>
To: Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a>>, "<a href="mailto:archivesspace@googlegroups.com">archivesspace@googlegroups.<wbr>com</a>" <<a href="mailto:archivesspace@googlegroups.com">archivesspace@googlegroups.<wbr>com</a>><br>
Subject: Re: [Archivesspace_Users_Group] Problems working with archival object with large number of direct children<br>
<br>
<br>
Hi all,<br>
<br>
As part of our new role as ArchivesSpace development partner, we will be addressing issues like this as a priority.<br>
<br>
It is still early days and we?re working with the folks at the ArchivesSpace program on a release schedule, so we can?t make any definitive statements yet, but please know that we are aware of this issue and will address it as soon as we are able.<br>
<br>
<br>
Cheers,<br>
James<br>
<br>
<br>
?<br>
James Bullen<br>
Hudson Molonglo<br>
<br>
<br>
<br>
On Nov 16, 2016, at 7:46 AM, Joshua D. Shaw <<a href="mailto:Joshua.D.Shaw@dartmouth.edu">Joshua.D.Shaw@dartmouth.edu</a><<wbr>mailto:<a href="mailto:Joshua.D.Shaw@dartmouth.edu">Joshua.D.Shaw@<wbr>dartmouth.edu</a>>> wrote:<br>
<br>
Hi all ?<br>
<br>
We at Dartmouth have experienced similar issues. We have some large resources as well (one has 60K+ objects in the tree) and anything that involves a save or rearrangement (moving a file around, etc) can take a *lot* of time (many minutes) and may cause an error ? typically of the ?another user is modifying this record? type.<br>
<br>
If we have to do any modifications to a resource of that size, we a) budget a lot of time and b) do things in small increments ? ie don?t move more than a couple of files around at a time. It?s not a great solution, but it does minimize some of the headache.<br>
<br>
I *think* (but haven?t had the time to really dig into this) that one reason the error comes about is because the indexer steps on/collides with the process that the save/arrangement kicked off. We are still running 1.3 and hope that some of our issues will be mitigated when we move to 1.5.1, though we know that not all of them have been resolved yet.<br>
<br>
One other data point is that we?ve got a plugin that runs as a background job doing a bunch of importing. This background job touches some of the larger resources, but does *not* cause the errors and long save times, which leads me to believe that a lot of the problem is in the frontend ? perhaps with the way the tree is populated - as Jason pointed out.<br>
<br>
Best,<br>
Joshua<br>
<br>
From: <<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-<wbr>bounces@lyralists.lyrasis.org</a><<wbr>mailto:<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_<wbr>group-bounces@lyralists.<wbr>lyrasis.org</a>>> on behalf of Jason Loeffler <<a href="mailto:j@minorscience.com">j@minorscience.com</a><mailto:<a href="mailto:j@minorscience.com">j@<wbr>minorscience.com</a>>><br>
Reply-To: Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a><mailto:<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">a<wbr>rchivesspace_users_group@<wbr>lyralists.lyrasis.org</a>>><br>
Date: Tuesday, November 15, 2016 at 3:25 PM<br>
To: Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a><mailto:<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">a<wbr>rchivesspace_users_group@<wbr>lyralists.lyrasis.org</a>>><br>
Cc: "<a href="mailto:archivesspace@googlegroups.com">archivesspace@googlegroups.<wbr>com</a><mailto:<a href="mailto:archivesspace@googlegroups.com">archivesspace@<wbr>googlegroups.com</a>>" <<a href="mailto:archivesspace@googlegroups.com">archivesspace@googlegroups.<wbr>com</a><mailto:<a href="mailto:archivesspace@googlegroups.com">archivesspace@<wbr>googlegroups.com</a>>><br>
Subject: Re: [Archivesspace_Users_Group] Problems working with archival object with large number of direct children<br>
<br>
Hi Sally,<br>
<br>
Definitely, yes. We have many resources with 5,000 or more archival object records. We've deployed on some pretty decent Amazon EC2 boxes (16GB memory, burstable CPU, etc.) with negligible improvement. I have a feeling that this is not a resource allocation issue. Looking at the web inspector, most of the time is spent negotiating jstree<<a href="http://jstree.com/" rel="noreferrer" target="_blank">http://jstree.com/</a>> and/or loading all JSON objects associated with a resource into the browser. Maybe an ASpace dev can weigh in.<br>
<br>
<br>
<br>
>From the sysadmin side, Maureen Callahan at Yale commissioned Percona to evaluate ArchivesSpace and MySQL performance. I've attached the report. Let me know if you need any help interpreting the report.<br>
<br>
At some point, and quite apart from this thread, I hope we can collectively revisit the staff interface architecture and recommend improvements.<br>
<br>
JL<br>
<br>
On Tue, Nov 15, 2016 at 2:37 PM, Sally Vermaaten <<a href="mailto:sally.vermaaten@nyu.edu">sally.vermaaten@nyu.edu</a><<wbr>mailto:<a href="mailto:sally.vermaaten@nyu.edu">sally.vermaaten@nyu.edu</a><wbr>>> wrote:<br>
Hi everyone,<br>
<br>
We're running into an issue with a large resource record in ArchivesSpace and wonder if anyone has experienced a similar issue. In one resource record, we have a series/archival object with around 19,000 direct children/archival objects. We've found that:<br>
? it takes several minutes to open the series in the 'tree' navigation view and then, once opened scrolling through series is very slow / laggy<br>
? it takes a couple of minutes to open any archival object in the series in edit mode and<br>
? it takes a couple of minutes to save changes to any archival object within the series<br>
Does anyone else have a similarly large archival object in a resource record? If so, have you observed the same long load/save time when editing the component records?<br>
<br>
The slow load time does not seem to be affected by memory allocation; we've tried increasing the speed / size of the server and it seemed to have no effect. We'd definitely appreciate any other suggestions for how we might fix or work around the problem.<br>
<br>
We also wonder if this performance issue is essentially caused by the queries being run to generate the UI view - i.e. perhaps in generating the resource 'tree' view, all data for the whole series (all 19k archival objects) is being retrieved and stored in memory? If so, we wondered if it would be possible and would make sense to change the queries running during tree generation, etc. to only retrieve some batches at a time, lazy loading style?<br>
<br>
Thanks,<br>
Weatherly and Sally<br>
<br>
--<br>
Sally Vermaaten<br>
Project Manager, Archival Systems<br>
New York University Libraries<br>
1-212-992-6259<tel:1-212-992-<wbr>6259><br>
<br>
______________________________<wbr>_________________<br>
Archivesspace_Users_Group mailing list<br>
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a><mailto:<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">A<wbr>rchivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a>><br>
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a><br>
<br>
!DSPAM:<wbr>582b7444314351074817778! ______________________________<wbr>_________________<br>
Archivesspace_Users_Group mailing list<br>
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a><mailto:<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">A<wbr>rchivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a>><br>
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a><br>
<br>
<br>
!DSPAM:<wbr>582b7444314351074817778!<br>
<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20161116/bf10e9c2/attachment-0001.html" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>pipermail/archivesspace_users_<wbr>group/attachments/20161116/<wbr>bf10e9c2/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 25<br>
Date: Wed, 16 Nov 2016 14:40:17 +0000<br>
From: Yvonne Kester <<a href="mailto:ykester@skidmore.edu">ykester@skidmore.edu</a>><br>
To: Archivesspace Users Group<br>
<<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a>><br>
Subject: Re: [Archivesspace_Users_Group] A user who is set as manager<br>
of a collection can not create containers...<br>
Message-ID:<br>
<<a href="mailto:BN1PR0101MB0865718BA7101988449621A9C7BE0@BN1PR0101MB0865.prod.exchangelabs.com">BN1PR0101MB0865718BA710198844<wbr>9621A9C7BE0@BN1PR0101MB0865.<wbr>prod.exchangelabs.com</a>><br>
<br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi Eric,<br>
<br>
We had a problem creating top containers a couple months ago. This is the answer I got from Christine:<br>
<br>
?There is a permission that needs to be added for the permission group that your user account is part of in order for you to create top containers. See the three options for containers below; there is also one for the new location profile functionality. Have your system administrator (or someone who otherwise has privileges that allow them to manage users) add any permissions you need to your permission group.<br>
<br>
[cid:image001.png@01D23FED.<wbr>6E85D7B0]<br>
<br>
(There?s information about managing users and permission groups in the manual at <a href="http://docs.archivesspace.org/Default.htm#UserPermGroupsManage.htm" rel="noreferrer" target="_blank">http://docs.archivesspace.org/<wbr>Default.htm#<wbr>UserPermGroupsManage.htm</a> )<br>
<br>
<br>
I hope this helps!<br>
Yvonne<br>
<br>
From: <a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-<wbr>bounces@lyralists.lyrasis.org</a> [mailto:<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_<wbr>group-bounces@lyralists.<wbr>lyrasis.org</a>] On Behalf Of Gadsby, Eric T.<br>
Sent: Tuesday, November 15, 2016 7:47 PM<br>
To: <a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a><br>
Subject: [Archivesspace_Users_Group] A user who is set as manager of a collection can not create containers...<br>
<br>
I posted this to the list earlier but the list seems more active this week so I thought I?d try again. One of ouse users is manger of a collection but can?t create containers in it here is what they report:<br>
<br>
?While attempting to create top containers for instances, I only had access to ?browse? but not create. I had management level access at the time. I had to be given admin level access to be able to gain the create button for top containers. The create option disappeared when placed on just admin level access. I had to be placed in both levels of access to be able to create top containers.?<br>
<br>
Our server has only been in production for a few weeks and is set-up per the <a href="http://www.archivesspace.org" rel="noreferrer" target="_blank">http://www.archivesspace.org</a> recommendations. Our server does authenticate via LDAP (Active Directory) but our users experience is the same using an AD or ArchivesSpace local users. Do you know how we might resolve this or what might be the next steps in troubleshooting? Thanks!<br>
<br>
Sincerely,<br>
<br>
Eric T Gadsby<br>
IT Operations Specialist, Cook Library<br>
Towson University<br>
<a href="mailto:egadsby@towson.edu">egadsby@towson.edu</a><mailto:<a href="mailto:egadsby@towson.edu">egad<wbr>sby@towson.edu</a>><br>
410-704-3340<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20161116/bfbb5215/attachment.html" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>pipermail/archivesspace_users_<wbr>group/attachments/20161116/<wbr>bfbb5215/attachment.html</a>><br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: image001.png<br>
Type: image/png<br>
Size: 20851 bytes<br>
Desc: image001.png<br>
URL: <<a href="http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20161116/bfbb5215/attachment.png" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>pipermail/archivesspace_users_<wbr>group/attachments/20161116/<wbr>bfbb5215/attachment.png</a>><br>
<br>
------------------------------<br>
<br>
______________________________<wbr>_________________<br>
Archivesspace_Users_Group mailing list<br>
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a><br>
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a><br>
<br>
<br>
End of Archivesspace_Users_Group Digest, Vol 40, Issue 2<br>
******************************<wbr>**************************<br>
______________________________<wbr>_________________<br>
Archivesspace_Users_Group mailing list<br>
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a><br>
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a><br>
</blockquote></div><br></div></div></div>