From michael_vandermillen at harvard.edu Wed Jul 5 11:20:35 2017 From: michael_vandermillen at harvard.edu (Vandermillen, Michael) Date: Wed, 5 Jul 2017 15:20:35 +0000 Subject: [Archivesspace_Users_Group] RC 2.1 indexing slow Message-ID: Hi, I'm finding indexing in rc2.1 to be very slow, much slower than 2.0. It starts off very fast with agents and subjects, but as soon it starts with resources, digital & archival objects, it's crawling. (I ran the db migr. script, deleted old solr index, and am running with plenty of memory - 24 g). I know we have 2 solr indexes with 2x, but like I said, this is substantially slower than 2.0. Anyone else experiencing this? Any thoughts on tweaking the config? Apologies if I'm overlooking something obvious :) Thanks- Michael Michael Vandermillen Digital Library Software Engineer Library Technology Services, Harvard University IT -------------- next part -------------- An HTML attachment was scrubbed... URL: From Kevin.Clair at du.edu Wed Jul 5 11:29:16 2017 From: Kevin.Clair at du.edu (Kevin Clair) Date: Wed, 5 Jul 2017 15:29:16 +0000 Subject: [Archivesspace_Users_Group] RC 2.1 indexing slow In-Reply-To: References: Message-ID: Hello, I don't have any tips for speeding it up, but I've also noticed this on our development system, with all the same configuration settings as with previous 2.* release candidates. Indexes that used to complete overnight for us take an entire day or more on 2.1.0-RC1. -k From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Vandermillen, Michael Sent: Wednesday, July 05, 2017 9:21 AM To: Archivesspace Users Group (archivesspace_users_group at lyralists.lyrasis.org) Subject: [Archivesspace_Users_Group] RC 2.1 indexing slow Hi, I'm finding indexing in rc2.1 to be very slow, much slower than 2.0. It starts off very fast with agents and subjects, but as soon it starts with resources, digital & archival objects, it's crawling. (I ran the db migr. script, deleted old solr index, and am running with plenty of memory - 24 g). I know we have 2 solr indexes with 2x, but like I said, this is substantially slower than 2.0. Anyone else experiencing this? Any thoughts on tweaking the config? Apologies if I'm overlooking something obvious :) Thanks- Michael Michael Vandermillen Digital Library Software Engineer Library Technology Services, Harvard University IT -------------- next part -------------- An HTML attachment was scrubbed... URL: From livsolis at utexas.edu Wed Jul 5 13:32:35 2017 From: livsolis at utexas.edu (Olivia S Solis) Date: Wed, 5 Jul 2017 12:32:35 -0500 Subject: [Archivesspace_Users_Group] Different subjects with identical labels Message-ID: Hello all, I am not sure how many ASpace users out there share the most recent issue I have encountered migrating data to ArchivesSpace. For a number of reasons, the Briscoe Center has decided to go with GeoNames as our canonical controlled vocabulary for subject/geographical terms. This is a recent adoption and much of the legacy EAD we use goes with Library of Congress Geographic terms, which we are mapping to GeoNames. We are using Islandora for our digital repository for item-level description. i.e. We're using the MODS hierarchicalGeographic element, which works well with GeoNames because GeoNames also uses a hierarchical system to classify its terms. So for individual MODS records for digital objects you can do something like city: "Paris", country: "France" for one record vs city: "Paris", state: "Texas" in another. There would be two instances of "Paris" in our cities taxonomies, distinguished from each other by their broader terms and associated URIs. There is no disambiguating information in the labels themselves. The difference between the cities in records is given by the broader state or country elements plus URIs. That works great for item-level description, but causes a number of problems for collection level description in ArchivesSpace. 1. It appears that ArchivesSpace won't let me create a subject of the same type (e.g. Geographic) from the same source (e.g. GeoNames) that has a label identical to another term classified with the same type/source. 2. Just for the sake of experimentation in our ASpace sandbox, I identified one of my "Paris" records as a cultural context term. It was difficult to know the difference between the two when I tried to apply the subject to a resource record. The autocomplete feature did not include any disambiguating information (e.g. from the Scope field or the identifier field in the subject records). The browser headers in the "Browse" subjects link don't include the Scope note either. 3. Even if I could create two GeoNames geographical subjects with the label "Paris", I'm not sure how to communicate to the ASpace end user the difference between the cities when they are applied to records. I can add notes in the "Scope" field for each subject record -- "France" and "Texas" -- to communicate the info, but the scope field for the terms doesn't appear in e.g. a resource record's linked subject. 4. Even if we apply the correct label, the human-readable disambiguating information ("Texas" vs. "France") won't export to our EAD and our end users might get confused about which Paris we mean, especially if there happens to be a collection with both the Paris in Texas and the Paris in France. In such a case would we include the two different "Paris" subjects plus "France" and "Texas"? Again, this illustrates a difference in item vs. collection-level description. We publish our EAD via a consortial regional portal hosted by the University of Texas, TARO, which is how researchers view our finding aids online. It's possible we'll open up the public interface, but we're not there yet. Has anyone else encountered these problems? I'm sure there is a solution/numerous possible solutions to the problems above, though it might mean altering the GeoNames label in ArchivesSpace to include the disambiguating information. Not exactly kosher if we say we're using GeoNames terms, but we might have to. We want to use the same controlled vocabulary terms regardless of system for global consistency, ease of maintenance etc. I can imagine a kind of customization where our EAD exporter could grab, e.g. the "Scope" field with the broader term's label and append it to the label for, in this example "Paris", surrounded by parentheses. But that presumes we can enter two different GeoNames/geographical terms "Paris". See screen shots with fake data. FYI, we are on ASpace version 1.5.3. Thanks, and hopefully I'm not the only one with this problem! -Olivia -- Olivia Solis, MSIS Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2017-07-05 at 11.35.49 AM.png Type: image/png Size: 100769 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2017-07-05 at 11.32.47 AM.png Type: image/png Size: 55472 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2017-07-05 at 11.42.54 AM.png Type: image/png Size: 88822 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2017-07-05 at 11.42.37 AM.png Type: image/png Size: 19364 bytes Desc: not available URL: From sdm7g at eservices.virginia.edu Wed Jul 5 21:47:17 2017 From: sdm7g at eservices.virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Thu, 6 Jul 2017 01:47:17 +0000 Subject: [Archivesspace_Users_Group] Different subjects with identical labels In-Reply-To: References: Message-ID: <52F71939-7829-49F7-95B4-F43C2813941C@eservices.virginia.edu> I think you need to use Texas or France as subdivisions of the subject. The scope note is just a note/comment for documentation, and doesn?t distinguish the two subjects as being different. If you encode it like this, it will allow both ?Paris ? France? and ?Paris ? Texas? . Will this work for you ? ? Steve Majewski / UVA [cid:8FF6B995-F62C-4098-952C-754E9476D30C at zyxel.com] [cid:FFE8CF28-CD1F-4EEF-8DF7-36CD963C387B at zyxel.com] On Jul 5, 2017, at 1:32 PM, Olivia S Solis > wrote: Hello all, I am not sure how many ASpace users out there share the most recent issue I have encountered migrating data to ArchivesSpace. For a number of reasons, the Briscoe Center has decided to go with GeoNames as our canonical controlled vocabulary for subject/geographical terms. This is a recent adoption and much of the legacy EAD we use goes with Library of Congress Geographic terms, which we are mapping to GeoNames. We are using Islandora for our digital repository for item-level description. i.e. We're using the MODS hierarchicalGeographic element, which works well with GeoNames because GeoNames also uses a hierarchical system to classify its terms. So for individual MODS records for digital objects you can do something like city: "Paris", country: "France" for one record vs city: "Paris", state: "Texas" in another. There would be two instances of "Paris" in our cities taxonomies, distinguished from each other by their broader terms and associated URIs. There is no disambiguating information in the labels themselves. The difference between the cities in records is given by the broader state or country elements plus URIs. That works great for item-level description, but causes a number of problems for collection level description in ArchivesSpace. 1. It appears that ArchivesSpace won't let me create a subject of the same type (e.g. Geographic) from the same source (e.g. GeoNames) that has a label identical to another term classified with the same type/source. 2. Just for the sake of experimentation in our ASpace sandbox, I identified one of my "Paris" records as a cultural context term. It was difficult to know the difference between the two when I tried to apply the subject to a resource record. The autocomplete feature did not include any disambiguating information (e.g. from the Scope field or the identifier field in the subject records). The browser headers in the "Browse" subjects link don't include the Scope note either. 3. Even if I could create two GeoNames geographical subjects with the label "Paris", I'm not sure how to communicate to the ASpace end user the difference between the cities when they are applied to records. I can add notes in the "Scope" field for each subject record -- "France" and "Texas" -- to communicate the info, but the scope field for the terms doesn't appear in e.g. a resource record's linked subject. 4. Even if we apply the correct label, the human-readable disambiguating information ("Texas" vs. "France") won't export to our EAD and our end users might get confused about which Paris we mean, especially if there happens to be a collection with both the Paris in Texas and the Paris in France. In such a case would we include the two different "Paris" subjects plus "France" and "Texas"? Again, this illustrates a difference in item vs. collection-level description. We publish our EAD via a consortial regional portal hosted by the University of Texas, TARO, which is how researchers view our finding aids online. It's possible we'll open up the public interface, but we're not there yet. Has anyone else encountered these problems? I'm sure there is a solution/numerous possible solutions to the problems above, though it might mean altering the GeoNames label in ArchivesSpace to include the disambiguating information. Not exactly kosher if we say we're using GeoNames terms, but we might have to. We want to use the same controlled vocabulary terms regardless of system for global consistency, ease of maintenance etc. I can imagine a kind of customization where our EAD exporter could grab, e.g. the "Scope" field with the broader term's label and append it to the label for, in this example "Paris", surrounded by parentheses. But that presumes we can enter two different GeoNames/geographical terms "Paris". See screen shots with fake data. FYI, we are on ASpace version 1.5.3. Thanks, and hopefully I'm not the only one with this problem! -Olivia -- Olivia Solis, MSIS Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: paris.edit.png Type: image/png Size: 328325 bytes Desc: paris.edit.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2paris.png Type: image/png Size: 540583 bytes Desc: 2paris.png URL: From livsolis at utexas.edu Thu Jul 6 09:36:55 2017 From: livsolis at utexas.edu (Olivia S Solis) Date: Thu, 6 Jul 2017 08:36:55 -0500 Subject: [Archivesspace_Users_Group] Different subjects with identical labels In-Reply-To: <52F71939-7829-49F7-95B4-F43C2813941C@eservices.virginia.edu> References: <52F71939-7829-49F7-95B4-F43C2813941C@eservices.virginia.edu> Message-ID: Hi Steven, Thank you for the fix! Yes, this would seem to be how I need to migrate the terms, solving all my problems above. Much obliged! Olivia On Wed, Jul 5, 2017 at 8:47 PM, Majewski, Steven Dennis (sdm7g) < sdm7g at eservices.virginia.edu> wrote: > I think you need to use Texas or France as subdivisions of the subject. > The scope note is just a note/comment for documentation, and doesn?t > distinguish the two subjects as being different. If you encode it like > this, it will allow both ?Paris ? France? and ?Paris ? Texas? . Will this > work for you ? ? Steve Majewski / UVA > > > > > > > > > > On Jul 5, 2017, at 1:32 PM, Olivia S Solis wrote: > > Hello all, > > I am not sure how many ASpace users out there share the most recent issue > I have encountered migrating data to ArchivesSpace. For a number of > reasons, the Briscoe Center has decided to go with GeoNames as our > canonical controlled vocabulary for subject/geographical terms. This is a > recent adoption and much of the legacy EAD we use goes with Library of > Congress Geographic terms, which we are mapping to GeoNames. We are using > Islandora for our digital repository for item-level description. i.e. We're > using the MODS hierarchicalGeographic > > element, which works well with GeoNames because GeoNames also uses a > hierarchical system to classify its terms. So for individual MODS records > for digital objects you can do something like city: "Paris", country: > "France" for one record vs city: "Paris", state: "Texas" in another. There > would be two instances of "Paris" in our cities taxonomies, distinguished > from each other by their broader terms and associated URIs. There is no > disambiguating information in the labels themselves. The difference between > the cities in records is given by the broader state or country elements > plus URIs. > > That works great for item-level description, but causes a number of > problems for collection level description in ArchivesSpace. > > 1. It appears that ArchivesSpace won't let me create a subject of the > same type (e.g. Geographic) from the same source (e.g. GeoNames) that has a > label identical to another term classified with the same type/source. > 2. Just for the sake of experimentation in our ASpace sandbox, I > identified one of my "Paris" records as a cultural context term. It was > difficult to know the difference between the two when I tried to apply the > subject to a resource record. The autocomplete feature did not include any > disambiguating information (e.g. from the Scope field or the identifier > field in the subject records). The browser headers in the "Browse" subjects > link don't include the Scope note either. > 3. Even if I could create two GeoNames geographical subjects with the > label "Paris", I'm not sure how to communicate to the ASpace end user the > difference between the cities when they are applied to records. I can add > notes in the "Scope" field for each subject record -- "France" and "Texas" > -- to communicate the info, but the scope field for the terms doesn't > appear in e.g. a resource record's linked subject. > 4. Even if we apply the correct label, the human-readable > disambiguating information ("Texas" vs. "France") won't export to our EAD > and our end users might get confused about which Paris we mean, especially > if there happens to be a collection with both the Paris in Texas and the > Paris in France. In such a case would we include the two different "Paris" > subjects plus "France" and "Texas"? Again, this illustrates a difference in > item vs. collection-level description. We publish our EAD via a consortial > regional portal hosted by the University of Texas, TARO, which is how > researchers view our finding aids online. It's possible we'll open up the > public interface, but we're not there yet. > > Has anyone else encountered these problems? I'm sure there is a > solution/numerous possible solutions to the problems above, though it might > mean altering the GeoNames label in ArchivesSpace to include the > disambiguating information. Not exactly kosher if we say we're using > GeoNames terms, but we might have to. We want to use the same controlled > vocabulary terms regardless of system for global consistency, ease of > maintenance etc. I can imagine a kind of customization where our EAD > exporter could grab, e.g. the "Scope" field with the broader term's label > and append it to the label for, in this example "Paris", surrounded by > parentheses. But that presumes we can enter two different > GeoNames/geographical terms "Paris". > > See screen shots with fake data. FYI, we are on ASpace version 1.5.3. > > Thanks, and hopefully I'm not the only one with this problem! > > -Olivia > > -- > Olivia Solis, MSIS > Metadata Coordinator > Dolph Briscoe Center for American History > The University of Texas at Austin > 2300 Red River St. Stop D1100 > Austin TX, 78712-1426 > (512) 232-8013 <(512)%20232-8013> > 11.32.47 AM.png> 2017-07-05 at 11.42.37 AM.png>_______________________ > ________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Olivia Solis, MSIS Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: paris.edit.png Type: image/png Size: 328325 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2paris.png Type: image/png Size: 540583 bytes Desc: not available URL: From jane.labarbara at mail.wvu.edu Thu Jul 6 11:03:28 2017 From: jane.labarbara at mail.wvu.edu (Jane LaBarbara) Date: Thu, 6 Jul 2017 15:03:28 +0000 Subject: [Archivesspace_Users_Group] Importing agents into ASpace that we already have Message-ID: Good morning, My department started populating our ASpace repository with some hand-entered information as well as a massive import of Resource Records, which included linked agents. Now, I'm working to import legacy accession records with the CSV, and I've run into an odd problem that I'm interested to see if anyone else has solved. (We're running v1.5.1 right now, if that matters.) I've noticed that, in some cases, if I import an accession record via the CSV file that includes a donor agent which already exists in ASpace, the pre-existing agent just gets linked to the newly imported accession record. This is great except for when I'm trying to import the donor's address info too-I realized the address info I was trying to import was not added to the pre-existing agent record. Once I noticed this, I thought I'd be smart and check the list of donors in my accession CSV against the agents already in ASpace. If the agent was already in ASpace, I added the address by hand then deleted the address from the CSV file. Then I imported the CSV file. It seems that, in at least a few cases, this resulted in the creation of a second agent, so we'll have to do a lot of merging of agent records. I am assuming that if the content of certain fields in the agent record I'm trying to import match those in an agent record already in ASpace, that will result in a merge rather than a duplicate agent creation. Does anyone know which fields I need to pay attention to? Thanks, Jane / Jane Metters LaBarbara Assistant Curator, West Virginia & Regional History Center West Virginia University Libraries (304) 293-0352 office jane.labarbara at mail.wvu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From bthomas at tsl.texas.gov Thu Jul 6 11:09:56 2017 From: bthomas at tsl.texas.gov (Brian Thomas) Date: Thu, 6 Jul 2017 15:09:56 +0000 Subject: [Archivesspace_Users_Group] Importing agents into ASpace that we already have In-Reply-To: References: Message-ID: I do not know everything about this specific issue by any means, but I can tell you to watch out for how you spell names in the csv if you are using the authority id function. We are implementing authority ids to actually de-dupe agents at point of import since the merger doesn't always work. BUT we have noticed that when you do this a misspelling in the name in the csv supersedes the correct spelling in the authority (which we are importing from the loc, or were until the loc made their change recently). Brian Thomas Electronic Records Specialist Texas State Library and Archives Commission 1201 Brazos Street Austin, TX 78701 PH: (512) 475-3374 e-mail: bthomas at tsl.texas.gov tsl.texas.gov [cid:image001.jpg at 01D029A2.37194C70] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Jane LaBarbara Sent: Thursday, July 06, 2017 10:03 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Importing agents into ASpace that we already have Good morning, My department started populating our ASpace repository with some hand-entered information as well as a massive import of Resource Records, which included linked agents. Now, I'm working to import legacy accession records with the CSV, and I've run into an odd problem that I'm interested to see if anyone else has solved. (We're running v1.5.1 right now, if that matters.) I've noticed that, in some cases, if I import an accession record via the CSV file that includes a donor agent which already exists in ASpace, the pre-existing agent just gets linked to the newly imported accession record. This is great except for when I'm trying to import the donor's address info too-I realized the address info I was trying to import was not added to the pre-existing agent record. Once I noticed this, I thought I'd be smart and check the list of donors in my accession CSV against the agents already in ASpace. If the agent was already in ASpace, I added the address by hand then deleted the address from the CSV file. Then I imported the CSV file. It seems that, in at least a few cases, this resulted in the creation of a second agent, so we'll have to do a lot of merging of agent records. I am assuming that if the content of certain fields in the agent record I'm trying to import match those in an agent record already in ASpace, that will result in a merge rather than a duplicate agent creation. Does anyone know which fields I need to pay attention to? Thanks, Jane / Jane Metters LaBarbara Assistant Curator, West Virginia & Regional History Center West Virginia University Libraries (304) 293-0352 office jane.labarbara at mail.wvu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5314 bytes Desc: image001.png URL: From hmerrick at colby.edu Thu Jul 6 12:03:01 2017 From: hmerrick at colby.edu (Hubert J. Merrick) Date: Thu, 6 Jul 2017 12:03:01 -0400 Subject: [Archivesspace_Users_Group] Suppression of Agent Headings Within Digital Objects Message-ID: <000701d2f671$5d804370$1880ca50$@colby.edu> Is there a way to suppress Agent headings without suppressing entire Digital Objects? We have encountered some problems with duplication of Subject/Agent headings, and we thought this could be alleviated by suppressing select Agent headings (which we want to retain), but if there is a straightforward way of doing this without suppressing entire digital objects (which we don't want to suppress) the method is eluding us. Are we missing something obvious? Any suggestions would be appreciated. James Merrick, Colbiana Coordinator Special Collections, Miller Library Colby College 5150 Mayflower Hill Waterville, Maine 04901 207-859-5154 hmerrick at colby.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From KennedyN at si.edu Fri Jul 7 08:56:25 2017 From: KennedyN at si.edu (Kennedy, Nancy) Date: Fri, 7 Jul 2017 12:56:25 +0000 Subject: [Archivesspace_Users_Group] Suppression of Agent Headings Within Digital Objects In-Reply-To: <000701d2f671$5d804370$1880ca50$@colby.edu> References: <000701d2f671$5d804370$1880ca50$@colby.edu> Message-ID: <4142170736420940ACB07EE9EECDC21F51B52DA5@si-msedag04.US.SINET.SI.EDU> James - Have you looked into the "publish" checkbox? I believe that only the agents set to 'publish' will appear in the PUI. (Sidebar: I'm curious about why you want to retain the duplicate heading, rather than merge? "Publish" would impact all occurrences of the agent, so if you needed to display the 'other' version in some cases, I think this won't work). Efficiently applying the "publish" setting could be a larger question, of course.. As would making it user-friendly to your staff, as it is not always easy to tell which agents are published. For what it's worth: exports do seem to include the unpublished agents, so if that is important to you, you'd need a different approach. You're focusing on DO here, but for example, I notice that the EAD exports do include unpublished Agents, regardless of 'include unpublished' export option. Nancy Nancy Kennedy Smithsonian Institution kennedyn at si.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Hubert J. Merrick Sent: Thursday, July 06, 2017 12:03 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Suppression of Agent Headings Within Digital Objects Is there a way to suppress Agent headings without suppressing entire Digital Objects? We have encountered some problems with duplication of Subject/Agent headings, and we thought this could be alleviated by suppressing select Agent headings (which we want to retain), but if there is a straightforward way of doing this without suppressing entire digital objects (which we don't want to suppress) the method is eluding us. Are we missing something obvious? Any suggestions would be appreciated. James Merrick, Colbiana Coordinator Special Collections, Miller Library Colby College 5150 Mayflower Hill Waterville, Maine 04901 207-859-5154 hmerrick at colby.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From rob.green at uni.edu Fri Jul 7 09:47:21 2017 From: rob.green at uni.edu (Rob Green) Date: Fri, 7 Jul 2017 08:47:21 -0500 Subject: [Archivesspace_Users_Group] Quick Question about Migrating from Archon 3.21 Message-ID: Hi! No difficult geeky questions, I promise! I'm leading my University's effort to bring Archon content into ArchivesSpace, and see that the migration manual is intended for moving from Archon 3.21-rev2 to ArchivesSpace 1.0.4. I'm thinking the most prudent approach will be to install ASpace 1.0.4 on our servers, do the migration, and then update to ASpace 2.0.x. >From your guys' experience, is there anything dumb / misguided / foolhardy / horrifying about that approach? Just want to cover my bases before committing to this approach... Thanks! Rob a.k.a. The New Guy *Rob Green *rob.green at uni.edu *Web Developer III* *Chair, Library Organizational Development Committee* *UNI P&S Council: At-Large Rep & Employee Relations Chair *Rod Library, University of Northern Iowa (Room 231) Cedar Falls, Iowa 50613-3675 | (319) 273-6273 about.me/robgreeniowa | "Campaigner" (ENFP) ** Report web problems via https://servicehub.uni.edu ** -------------- next part -------------- An HTML attachment was scrubbed... URL: From crluers at wm.edu Fri Jul 7 10:21:33 2017 From: crluers at wm.edu (Luers, Christina) Date: Fri, 7 Jul 2017 14:21:33 +0000 Subject: [Archivesspace_Users_Group] Quick Question about Migrating from Archon 3.21 In-Reply-To: References: Message-ID: Hi Rob, We are migrating from Archon to Archives Space as I type. It has not been an easy endeavor mostly due to inconsistencies in how we entered collections. For instance, if your container lists do not have either a title or a date (they just say box 1, for instance), then they will not transfer properly and the migration will fail. We have found that with our +7000 collections, it has been best to export the Archon container lists into a spreadsheet. (we used Yale?s set up for that) and then we are all working to fix and fill in the missing metadata. This is just phase I of our migration process. Essentially, what I am saying is that we have found no easy way to move from Archon to ASpace and have discovered that if we export our metadata into EAD and spreadsheets for container lists, it makes for a much easier time of getting our metadata into ASpace. Good luck with your migration and please let me know how it is going for you. Maybe we can learn a thing or two from you and also share fixes as you move into ASpace from Archon. Sincerely, Tina Luers Archives Collections Specialist College of William and Mary From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Rob Green Sent: Friday, July 07, 2017 9:47 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Quick Question about Migrating from Archon 3.21 Hi! No difficult geeky questions, I promise! I'm leading my University's effort to bring Archon content into ArchivesSpace, and see that the migration manual is intended for moving from Archon 3.21-rev2 to ArchivesSpace 1.0.4. I'm thinking the most prudent approach will be to install ASpace 1.0.4 on our servers, do the migration, and then update to ASpace 2.0.x. From your guys' experience, is there anything dumb / misguided / foolhardy / horrifying about that approach? Just want to cover my bases before committing to this approach... Thanks! Rob a.k.a. The New Guy Rob Green rob.green at uni.edu Web Developer III Chair, Library Organizational Development Committee UNI P&S Council: At-Large Rep & Employee Relations Chair Rod Library, University of Northern Iowa (Room 231) Cedar Falls, Iowa 50613-3675 | (319) 273-6273 about.me/robgreeniowa | "Campaigner" (ENFP) * Report web problems via https://servicehub.uni.edu * -------------- next part -------------- An HTML attachment was scrubbed... URL: From brian.harrington at lyrasis.org Fri Jul 7 10:27:41 2017 From: brian.harrington at lyrasis.org (Brian Harrington) Date: Fri, 7 Jul 2017 14:27:41 +0000 Subject: [Archivesspace_Users_Group] Quick Question about Migrating from Archon 3.21 In-Reply-To: References: Message-ID: Hi Rob, It looks like the manual is out of date. The latest version of the ArchonMigrator tool https://github.com/archivesspace/ArchonMigrator supports 1.4.2 (the last release before the container management features were added). Other than that, I would say you have the right approach. Archon -> ASpace 1.4.2 -> the current version of ASpace. I do this semi-regularly, and it works well. Now for the geeky questions. :-) Brian ? Brian Harrington Migration Specialist LYRASIS brian.harrington at lyrasis.org Skype: abbistani > On Jul 7, 2017, at 9:47 AM, Rob Green wrote: > > Hi! No difficult geeky questions, I promise! > > I'm leading my University's effort to bring Archon content into ArchivesSpace, and see that the migration manual is intended for moving from Archon 3.21-rev2 to ArchivesSpace 1.0.4. I'm thinking the most prudent approach will be to install ASpace 1.0.4 on our servers, do the migration, and then update to ASpace 2.0.x. > > From your guys' experience, is there anything dumb / misguided / foolhardy / horrifying about that approach? Just want to cover my bases before committing to this approach... > > Thanks! > Rob > > a.k.a. The New Guy > > > > Rob Green rob.green at uni.edu > Web Developer III > Chair, Library Organizational Development Committee > UNI P&S Council: At-Large Rep & Employee Relations Chair > Rod Library, University of Northern Iowa (Room 231) > Cedar Falls, Iowa 50613-3675 | (319) 273-6273 > about.me/robgreeniowa | "Campaigner" (ENFP) > > * Report web problems via https://servicehub.uni.edu * > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group From ccrist at eastman.org Fri Jul 7 12:04:59 2017 From: ccrist at eastman.org (Cheri Crist) Date: Fri, 7 Jul 2017 12:04:59 -0400 Subject: [Archivesspace_Users_Group] Show more than 10 results in Instances dropdown Message-ID: When I type box into the top container field in an instance, the results only show the first 10 (i.e., Box 1, Box 2, etc.). If I want to enter anything above box 10, I have to browse for it, which is becoming time-consuming and tedious. I feel like there must be something I'm missing. Any help is appreciated! Thank you, Cheri Cheri Crist Project Archivist Richard and Ronay Menschel Library George Eastman Museum 900 East Ave. Rochester, NY 14607 ccrist at eastman.org (585)271-3361 ext. 280 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: instances.png Type: image/png Size: 286934 bytes Desc: not available URL: From christine.dibella at lyrasis.org Fri Jul 7 12:26:54 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Fri, 7 Jul 2017 16:26:54 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace release candidate available - v2.1.0_RC2 Message-ID: Dear ArchivesSpace members, Thank you so much to all who submitted feedback on v2.1.0-RC1. Your efforts have helped us identify and address a number of bugs and performance issues prior to the production version of this major release. Because a number of issues were addressed throughout the application, we have decided to make an additional release candidate available for a very short period of time. V2.1.0_RC2 (https://github.com/archivesspace/archivesspace/releases/tag/v2.1.0_RC2) is now available for download and testing purposes. Please email me directly with any issues or questions. Thanks again for your efforts and feedback. Barring unforeseen issues, we expect the production release of 2.1.0 to come out next week. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 13904 bytes Desc: image001.jpg URL: From mmwisner at fas.harvard.edu Fri Jul 7 12:50:15 2017 From: mmwisner at fas.harvard.edu (Wisner, Melanie) Date: Fri, 7 Jul 2017 16:50:15 +0000 Subject: [Archivesspace_Users_Group] Show more than 10 results in Instances dropdown In-Reply-To: References: Message-ID: Just type in the number you want, not ?box?. If it exists, it should show up for you to select. cheers, Melanie . . . . . . . Melanie Wisner, CA Accessioning Archivist Houghton Library, Harvard University Cambridge, MA 02138 US 617.384.7373 mmwisner at fas.harvard.edu [H75_Logo_Email_Prussian_Blue] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Cheri Crist Sent: Friday, July 07, 2017 12:05 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Show more than 10 results in Instances dropdown When I type box into the top container field in an instance, the results only show the first 10 (i.e., Box 1, Box 2, etc.). If I want to enter anything above box 10, I have to browse for it, which is becoming time-consuming and tedious. I feel like there must be something I'm missing. Any help is appreciated! Thank you, Cheri Cheri Crist Project Archivist Richard and Ronay Menschel Library George Eastman Museum 900 East Ave. Rochester, NY 14607 ccrist at eastman.org (585)271-3361 ext. 280 [Image removed by sender.] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 11324 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 413 bytes Desc: image002.jpg URL: From james at hudmol.com Sun Jul 9 21:12:31 2017 From: james at hudmol.com (James Bullen) Date: Mon, 10 Jul 2017 11:12:31 +1000 Subject: [Archivesspace_Users_Group] ArchivesSpace developers in Portland Message-ID: Hello ArchivesSpace developers, Are you interested in getting together in Portland? Mark Triggs and I will be there and would love to meet up with other people developing with ArchivesSpace. If you?re interested, please contact me off list. Cheers, James ? James Bullen Director/Developer, Hudson Molonglo ArchivesSpace Development Partner From jmargalo at udel.edu Mon Jul 10 15:46:37 2017 From: jmargalo at udel.edu (Jaime Margalotti) Date: Mon, 10 Jul 2017 15:46:37 -0400 Subject: [Archivesspace_Users_Group] Index Formatting Question Message-ID: I've been cleaning up old imports and found one with a wonky index. A little bit of searching shows that this isn't an uncommon issue. Before I clean it up, I just want to confirm formatting. In the "Reference" field, would I simply need to include the text of the component level identifier (for example: V.3_343) or would I need to format it as href ="V.3_343"? Along with the component-level id="V.3_343" tag, the original encoding on the index end was: Agatha, Mother. v. 3, p. 343 Thanks, Jaime -- Jaime L. Margalotti Associate Librarian Manuscripts and Archives Department University of Delaware Library Newark, DE 19717-5267 302-831-0554jmargalo at udel.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From ccauste1 at swarthmore.edu Tue Jul 11 09:37:09 2017 From: ccauste1 at swarthmore.edu (Celia Caust-Ellenbogen) Date: Tue, 11 Jul 2017 09:37:09 -0400 Subject: [Archivesspace_Users_Group] Indexing woes in v 2.0.1 Message-ID: Hello all, We just upgraded to v 2.0.1 and now the indexer doesn't seem to be working properly - not in the staff interface nor in the PUI. We can create and change records, and when you are viewing the individual record it is correctly updated in both Public and Staff. However, these changes are not reflected in the browse/search in either Public or Staff. Old deleted records are still showing up in browse/search while new records cannot be found in browse/search. Any ideas for how to fix this? Following a suggestion on this listserv, we already tried forcing a re-index by stopping the application, deleting the following directories, and restarting Archivesspace /path/to/archivespace*/data/solr_index/index/* /path/to/archivesspace*/data/indexer_pui_state* /path/to/archivesspace*/data/indexer_state* This updated the index in terms of old activity, but new activity is still not being captured. We would appreciate any suggestions for what to try next. Thanks! Celia -- Celia Caust-Ellenbogen Friends Historical Library of Swarthmore College 610-328-8498 ccauste1 at swarthmore.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From clobdel1 at swarthmore.edu Tue Jul 11 10:32:42 2017 From: clobdel1 at swarthmore.edu (Chelsea Lobdell) Date: Tue, 11 Jul 2017 10:32:42 -0400 Subject: [Archivesspace_Users_Group] Indexing woes in v 2.0.1 In-Reply-To: References: Message-ID: To add to Celia's post, we originally planned an upgrade from v1.5.3 to v2.0.1 because our Archivesspace instance was experience extreme periods of slowness with CPU usage going upwards of 95-98%. The log was full of Java out of memory errors. Following the upgrade we increased the RAM on the server from 2G to 4G and increased the CPUs from 2 to 4 as well. When indexing issues were first reported I ran scripts/checkindex.sh data/solr_index/index which reported no issues with the index. However, it was evident that there was something a miss with the solr index. Which led to the deletion of the following directories to for an entire re-index: /path/to/archivespace*/data/solr_index/index/* /path/to/archivesspace*/data/indexer_pui_state* /path/to/archivesspace*/data/indexer_state* As Celia notes, this corrected issues for items that were added / modified previously but going forward addition / modification / deletions are not behaving properly in search and browse. Also, the Solr log continue to be full of sever errors that all follow the pattern below: org.apache.solr.common.SolrException: Exception writing document id /repositories/6/resources/8766 to the index; possible analysis error. at org.apache.solr.update.DirectUpdateHandler2.addDoc(DirectUpdateHandler2.java:168) at org.apache.solr.update.processor.RunUpdateProcessor.processAdd(RunUpdateProcessorFactory.java:69) ... Caused by: org.apache.lucene.store.AlreadyClosedException: this IndexWriter is closed at org.apache.lucene.index.IndexWriter.ensureOpen(IndexWriter.java:700) at org.apache.lucene.index.IndexWriter.ensureOpen(IndexWriter.java:714) ... 40 more Caused by: java.lang.OutOfMemoryError: GC overhead limit exceeded I've been using JVM Top to monitor heap, GC, and CPU but so far I have not been able to draw any helpful conclusion from the data. Any advice / suggestions on what to try from here would be greatly appreciated. - Chelsea *---------------* *Chelsea Lobdell* *Library Web Developer/ Swarthmore College* *clobdel1 at swarthmore.edu / (610)690-6818* On Tue, Jul 11, 2017 at 9:37 AM, Celia Caust-Ellenbogen < ccauste1 at swarthmore.edu> wrote: > Hello all, > > We just upgraded to v 2.0.1 and now the indexer doesn't seem to be working > properly - not in the staff interface nor in the PUI. We can create and > change records, and when you are viewing the individual record it is > correctly updated in both Public and Staff. However, these changes are not > reflected in the browse/search in either Public or Staff. Old deleted > records are still showing up in browse/search while new records cannot be > found in browse/search. > > Any ideas for how to fix this? > > Following a suggestion on this listserv, we already tried forcing a > re-index by stopping the application, deleting the following directories, > and restarting Archivesspace > > /path/to/archivespace*/data/solr_index/index/* > > /path/to/archivesspace*/data/indexer_pui_state* > /path/to/archivesspace*/data/indexer_state* > > This updated the index in terms of old activity, but new activity is still > not being captured. > > We would appreciate any suggestions for what to try next. > > Thanks! > Celia > > -- > Celia Caust-Ellenbogen > Friends Historical Library of Swarthmore College > > 610-328-8498 <(610)%20328-8498> > ccauste1 at swarthmore.edu > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Tue Jul 11 11:29:39 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Tue, 11 Jul 2017 15:29:39 +0000 Subject: [Archivesspace_Users_Group] Indexing woes in v 2.0.1 In-Reply-To: References: Message-ID: Hi Celia and Chelsea, Since it sounds like this may be fairly specific to your setup and data, I?m going to put a tech support ticket in for you (you?ll see a separate message directly to you about that in a minute). When it gets worked out, it?d be great if you?d post the solution back to the list. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chelsea Lobdell Sent: Tuesday, July 11, 2017 10:33 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Indexing woes in v 2.0.1 To add to Celia's post, we originally planned an upgrade from v1.5.3 to v2.0.1 because our Archivesspace instance was experience extreme periods of slowness with CPU usage going upwards of 95-98%. The log was full of Java out of memory errors. Following the upgrade we increased the RAM on the server from 2G to 4G and increased the CPUs from 2 to 4 as well. When indexing issues were first reported I ran scripts/checkindex.sh data/solr_index/index which reported no issues with the index. However, it was evident that there was something a miss with the solr index. Which led to the deletion of the following directories to for an entire re-index: /path/to/archivespace/data/solr_index/index/ /path/to/archivesspace/data/indexer_pui_state /path/to/archivesspace/data/indexer_state As Celia notes, this corrected issues for items that were added / modified previously but going forward addition / modification / deletions are not behaving properly in search and browse. Also, the Solr log continue to be full of sever errors that all follow the pattern below: org.apache.solr.common.SolrException: Exception writing document id /repositories/6/resources/8766 to the index; possible analysis error. at org.apache.solr.update.DirectUpdateHandler2.addDoc(DirectUpdateHandler2.java:168) at org.apache.solr.update.processor.RunUpdateProcessor.processAdd(RunUpdateProcessorFactory.java:69) ... Caused by: org.apache.lucene.store.AlreadyClosedException: this IndexWriter is closed at org.apache.lucene.index.IndexWriter.ensureOpen(IndexWriter.java:700) at org.apache.lucene.index.IndexWriter.ensureOpen(IndexWriter.java:714) ... 40 more Caused by: java.lang.OutOfMemoryError: GC overhead limit exceeded I've been using JVM Top to monitor heap, GC, and CPU but so far I have not been able to draw any helpful conclusion from the data. Any advice / suggestions on what to try from here would be greatly appreciated. - Chelsea --------------- Chelsea Lobdell Library Web Developer/ Swarthmore College clobdel1 at swarthmore.edu / (610)690-6818 On Tue, Jul 11, 2017 at 9:37 AM, Celia Caust-Ellenbogen > wrote: Hello all, We just upgraded to v 2.0.1 and now the indexer doesn't seem to be working properly - not in the staff interface nor in the PUI. We can create and change records, and when you are viewing the individual record it is correctly updated in both Public and Staff. However, these changes are not reflected in the browse/search in either Public or Staff. Old deleted records are still showing up in browse/search while new records cannot be found in browse/search. Any ideas for how to fix this? Following a suggestion on this listserv, we already tried forcing a re-index by stopping the application, deleting the following directories, and restarting Archivesspace /path/to/archivespace/data/solr_index/index/ /path/to/archivesspace/data/indexer_pui_state /path/to/archivesspace/data/indexer_state This updated the index in terms of old activity, but new activity is still not being captured. We would appreciate any suggestions for what to try next. Thanks! Celia -- Celia Caust-Ellenbogen Friends Historical Library of Swarthmore College 610-328-8498 ccauste1 at swarthmore.edu _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 13904 bytes Desc: image001.jpg URL: From REedwards at getty.edu Tue Jul 11 12:02:39 2017 From: REedwards at getty.edu (Ryan Edwards) Date: Tue, 11 Jul 2017 16:02:39 +0000 Subject: [Archivesspace_Users_Group] Indexing woes in v 2.0.1 In-Reply-To: References: Message-ID: Hello, We had the same problems with the index being corrupted after upgrading from version 1.5.1 to 2.0.1. Our server has a lot of RAM, but only one CPU. After, backing up our mysql database, I stopped the application, blew away the entire /path/to/archivespace/data directory, and restarted the application, which rebuilt our indexes. Performance improved, but the application is still running slower than it did before on version 1.5.1. We are experimenting now with moving the mysql database and/or solr index as well as moving the application to the Amazon AWS cloud. Hopefully in the future, as the ArchivesSpace software is improved, it will run more efficiently and require fewer resources. -Ryan Ryan Edwards Digital Access and Systems Librarian Information Systems Getty Research Institute 1200 Getty Center Drive, Suite 1100 Los Angeles, CA 90049-1688 reedwards at getty.edu 310.440.7398 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Christine Di Bella Sent: Tuesday, July 11, 2017 8:30 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Indexing woes in v 2.0.1 Hi Celia and Chelsea, Since it sounds like this may be fairly specific to your setup and data, I?m going to put a tech support ticket in for you (you?ll see a separate message directly to you about that in a minute). When it gets worked out, it?d be great if you?d post the solution back to the list. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chelsea Lobdell Sent: Tuesday, July 11, 2017 10:33 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Indexing woes in v 2.0.1 To add to Celia's post, we originally planned an upgrade from v1.5.3 to v2.0.1 because our Archivesspace instance was experience extreme periods of slowness with CPU usage going upwards of 95-98%. The log was full of Java out of memory errors. Following the upgrade we increased the RAM on the server from 2G to 4G and increased the CPUs from 2 to 4 as well. When indexing issues were first reported I ran scripts/checkindex.sh data/solr_index/index which reported no issues with the index. However, it was evident that there was something a miss with the solr index. Which led to the deletion of the following directories to for an entire re-index: /path/to/archivespace/data/solr_index/index/ /path/to/archivesspace/data/indexer_pui_state /path/to/archivesspace/data/indexer_state As Celia notes, this corrected issues for items that were added / modified previously but going forward addition / modification / deletions are not behaving properly in search and browse. Also, the Solr log continue to be full of sever errors that all follow the pattern below: org.apache.solr.common.SolrException: Exception writing document id /repositories/6/resources/8766 to the index; possible analysis error. at org.apache.solr.update.DirectUpdateHandler2.addDoc(DirectUpdateHandler2.java:168) at org.apache.solr.update.processor.RunUpdateProcessor.processAdd(RunUpdateProcessorFactory.java:69) ... Caused by: org.apache.lucene.store.AlreadyClosedException: this IndexWriter is closed at org.apache.lucene.index.IndexWriter.ensureOpen(IndexWriter.java:700) at org.apache.lucene.index.IndexWriter.ensureOpen(IndexWriter.java:714) ... 40 more Caused by: java.lang.OutOfMemoryError: GC overhead limit exceeded I've been using JVM Top to monitor heap, GC, and CPU but so far I have not been able to draw any helpful conclusion from the data. Any advice / suggestions on what to try from here would be greatly appreciated. - Chelsea --------------- Chelsea Lobdell Library Web Developer/ Swarthmore College clobdel1 at swarthmore.edu / (610)690-6818 On Tue, Jul 11, 2017 at 9:37 AM, Celia Caust-Ellenbogen > wrote: Hello all, We just upgraded to v 2.0.1 and now the indexer doesn't seem to be working properly - not in the staff interface nor in the PUI. We can create and change records, and when you are viewing the individual record it is correctly updated in both Public and Staff. However, these changes are not reflected in the browse/search in either Public or Staff. Old deleted records are still showing up in browse/search while new records cannot be found in browse/search. Any ideas for how to fix this? Following a suggestion on this listserv, we already tried forcing a re-index by stopping the application, deleting the following directories, and restarting Archivesspace /path/to/archivespace/data/solr_index/index/ /path/to/archivesspace/data/indexer_pui_state /path/to/archivesspace/data/indexer_state This updated the index in terms of old activity, but new activity is still not being captured. We would appreciate any suggestions for what to try next. Thanks! Celia -- Celia Caust-Ellenbogen Friends Historical Library of Swarthmore College 610-328-8498 ccauste1 at swarthmore.edu _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 4073 bytes Desc: image002.jpg URL: From kate_bowers at harvard.edu Tue Jul 11 12:26:13 2017 From: kate_bowers at harvard.edu (Bowers, Kate A.) Date: Tue, 11 Jul 2017 16:26:13 +0000 Subject: [Archivesspace_Users_Group] "share" boxes / group boxes Message-ID: On Yale's (very helpful) web site http://guides.library.yale.edu/archivesspace/ASpaceContainerManagement there is this intriguing mention: The ability to "share" boxes across entire collections in a meaningful way. Let's say that you want to put all of the panoramic photos in your repository into the same container. With this new data model, you'll be able to keep much better control over that container. However, I've not been able to figure out how this ought to be done. Is anyone using AS to share boxes across multiple collections? If so, would you be willing to send a few screenshots or any documentation that you have? I'd be very grateful! Thanks, Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives kate_bowers at harvard.edu voice: (617) 998-5238 fax: (617) 495-8011 web: http://nrs.harvard.edu/urn-3:hul.eresource:archives Twitter: @k8_bowers -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.custer at yale.edu Tue Jul 11 12:43:52 2017 From: mark.custer at yale.edu (Custer, Mark) Date: Tue, 11 Jul 2017 16:43:52 +0000 Subject: [Archivesspace_Users_Group] "share" boxes / group boxes In-Reply-To: References: Message-ID: Kate, When linking a top container in this way, you just need to go to "Browse" instead of Create. On the Browse list, just find the top container that you want to link to from whatever context and then link to it (it's often easiest to search for the other collection's finding aid title, for instance). Here's an example from the ArchivesSpace sandbox: http://sandbox.archivesspace.org/top_containers/7 You'll see that /top_containers/7 is shared by two different collections in the same repository. The only catch is that you can only share a top container if and only if it's part of the same repository. Sorry for the lack of screenshots, but hopefully that makes sense. If not, I can write something else up later today. All my best, Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Bowers, Kate A. Sent: Tuesday, 11 July, 2017 12:26 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] "share" boxes / group boxes On Yale's (very helpful) web site http://guides.library.yale.edu/archivesspace/ASpaceContainerManagement there is this intriguing mention: The ability to "share" boxes across entire collections in a meaningful way. Let's say that you want to put all of the panoramic photos in your repository into the same container. With this new data model, you'll be able to keep much better control over that container. However, I've not been able to figure out how this ought to be done. Is anyone using AS to share boxes across multiple collections? If so, would you be willing to send a few screenshots or any documentation that you have? I'd be very grateful! Thanks, Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives kate_bowers at harvard.edu voice: (617) 998-5238 fax: (617) 495-8011 web: http://nrs.harvard.edu/urn-3:hul.eresource:archives Twitter: @k8_bowers -------------- next part -------------- An HTML attachment was scrubbed... URL: From laurie.arp at lyrasis.org Tue Jul 11 14:30:13 2017 From: laurie.arp at lyrasis.org (Laurie Arp) Date: Tue, 11 Jul 2017 18:30:13 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace 4th Quarter Board update Message-ID: Forwarding on behalf of Carol Mandel... Dear ArchivesSpace members, I am writing to report on the ArchivesSpace Governance Board 4th Quarter meeting, a 2 hour conference call which was conducted June 2nd. The board approved the nominations to the Governance board, and appointments to the Technical Advisory Council and User Advisory Council. We thanked the Nominations Committee, chaired by Gerald (Jay) Gaidmore. Jay will send out an announcement of the election and appointment results once the Governance Board election is complete. We reviewed: * the continued excellent work of TAC and UAC and thank the members for their dedicated participation * an operational update that indicates good progress on development work by HM, the creation of a core committers group and progress in our recruitment for a Community Engagement Coordinator * a financial report that confirms we are on budget and in a strong financial position The board members thanked departing Board members Gerald (Jay) Gaidmore and Brian Schottlaender for their active and substantial service on the board. Jay has served for two terms and has been on the board since its inception. As one of the inaugural board members his early insight and dedication were especially valuable. Some of Jay's contributions include chairing the 2017 Nominating Committee, serving as the Board liaison to the Technical Advisory Council, and representing the Governance Board in the ArchivesSpace Program Manager search. Brian retired from his position as the Audrey Geisel University Librarian at UC San Diego (UCSD) on June 30 and thus is leaving the board but UCSD remains a partner and continues to be represented on the board. Brian played a leading role in the creation of the ArchivesSpace software and the ArchivesSpace community since the inception of the program. Brian served as a founding partner on the ArchivesSpace Governance Board with unstinting dedication and outstanding participation. Brian was instrumental in creating the membership and governance models, recruiting colleagues to be charter members, and in bylaws creation. Their contributions have played a critical role in the success of ArchivesSpace. The Board very much appreciates their commitment, skills and devotion to furthering the ArchivesSpace community. In closing, I am very happy to report that the ArchivesSpace membership organization is vibrant and is growing at a steady rate. Members are participating in all facets of the program and continue to be its strongest advocates. The Board welcomes your communications and comments on any and all of us, and we extend our thanks to all of you for your continuing support and ongoing contributions to the community we have created. Respectfully, Carol A. Mandel Chair, ArchivesSpace Governance Board Dean, Division of Libraries, New York University -------------- next part -------------- An HTML attachment was scrubbed... URL: From kate_bowers at harvard.edu Tue Jul 11 14:50:49 2017 From: kate_bowers at harvard.edu (Bowers, Kate A.) Date: Tue, 11 Jul 2017 18:50:49 +0000 Subject: [Archivesspace_Users_Group] "share" boxes / group boxes In-Reply-To: References: Message-ID: Is this how you are using it in real life? Also: did you have shared containers you needed to ingest? (We have about 10,000 of them holding about 60,000-70,000 things). Kate From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Custer, Mark Sent: Tuesday, July 11, 2017 12:44 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] "share" boxes / group boxes Kate, When linking a top container in this way, you just need to go to "Browse" instead of Create. On the Browse list, just find the top container that you want to link to from whatever context and then link to it (it's often easiest to search for the other collection's finding aid title, for instance). Here's an example from the ArchivesSpace sandbox: http://sandbox.archivesspace.org/top_containers/7 You'll see that /top_containers/7 is shared by two different collections in the same repository. The only catch is that you can only share a top container if and only if it's part of the same repository. Sorry for the lack of screenshots, but hopefully that makes sense. If not, I can write something else up later today. All my best, Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Bowers, Kate A. Sent: Tuesday, 11 July, 2017 12:26 PM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] "share" boxes / group boxes On Yale's (very helpful) web site http://guides.library.yale.edu/archivesspace/ASpaceContainerManagement there is this intriguing mention: The ability to "share" boxes across entire collections in a meaningful way. Let's say that you want to put all of the panoramic photos in your repository into the same container. With this new data model, you'll be able to keep much better control over that container. However, I've not been able to figure out how this ought to be done. Is anyone using AS to share boxes across multiple collections? If so, would you be willing to send a few screenshots or any documentation that you have? I'd be very grateful! Thanks, Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives kate_bowers at harvard.edu voice: (617) 998-5238 fax: (617) 495-8011 web: http://nrs.harvard.edu/urn-3:hul.eresource:archives Twitter: @k8_bowers -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.custer at yale.edu Tue Jul 11 15:12:24 2017 From: mark.custer at yale.edu (Custer, Mark) Date: Tue, 11 Jul 2017 19:12:24 +0000 Subject: [Archivesspace_Users_Group] "share" boxes / group boxes In-Reply-To: References: Message-ID: Nope, we did not have any shared containers to ingest, but this is how we'd use the feature in a normal workflow in the staff interface. That said, a feature request that's still needed in ASpace is a "top container merge" feature (see https://archivesspace.atlassian.net/browse/AR-1436). If you had that, it would make it slightly easier in the staff interface, but still not something you'd want to do for anything at scale. As for pre-existing data and making any updates at scale, I think you'd want to handle this with the API. If we were doing EAD imports with shared containers, though, I suspect we'd follow the Bentley's lead on how they imported Subjects/Agents by 1) creating the top container records first, and 2) updating the EAD import process so that the match would be on the ASpace top container URI rather than creating a new top container per unique container indicator string. Either way, the only way that I could think to do this would be to rely on the ASpace top container URL, which looks something like this in the JSON record: "top_container": {"ref":"/repositories/2/top_containers/3000"}. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Bowers, Kate A. Sent: Tuesday, 11 July, 2017 2:51 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] "share" boxes / group boxes Is this how you are using it in real life? Also: did you have shared containers you needed to ingest? (We have about 10,000 of them holding about 60,000-70,000 things). Kate From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Custer, Mark Sent: Tuesday, July 11, 2017 12:44 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] "share" boxes / group boxes Kate, When linking a top container in this way, you just need to go to "Browse" instead of Create. On the Browse list, just find the top container that you want to link to from whatever context and then link to it (it's often easiest to search for the other collection's finding aid title, for instance). Here's an example from the ArchivesSpace sandbox: http://sandbox.archivesspace.org/top_containers/7 You'll see that /top_containers/7 is shared by two different collections in the same repository. The only catch is that you can only share a top container if and only if it's part of the same repository. Sorry for the lack of screenshots, but hopefully that makes sense. If not, I can write something else up later today. All my best, Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Bowers, Kate A. Sent: Tuesday, 11 July, 2017 12:26 PM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] "share" boxes / group boxes On Yale's (very helpful) web site http://guides.library.yale.edu/archivesspace/ASpaceContainerManagement there is this intriguing mention: The ability to "share" boxes across entire collections in a meaningful way. Let's say that you want to put all of the panoramic photos in your repository into the same container. With this new data model, you'll be able to keep much better control over that container. However, I've not been able to figure out how this ought to be done. Is anyone using AS to share boxes across multiple collections? If so, would you be willing to send a few screenshots or any documentation that you have? I'd be very grateful! Thanks, Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives kate_bowers at harvard.edu voice: (617) 998-5238 fax: (617) 495-8011 web: http://nrs.harvard.edu/urn-3:hul.eresource:archives Twitter: @k8_bowers -------------- next part -------------- An HTML attachment was scrubbed... URL: From alicia.detelich at yale.edu Tue Jul 11 15:51:19 2017 From: alicia.detelich at yale.edu (Detelich, Alicia) Date: Tue, 11 Jul 2017 19:51:19 +0000 Subject: [Archivesspace_Users_Group] "share" boxes / group boxes In-Reply-To: References: Message-ID: Hi Kate, This use case may be slightly different than what you had in mind, but one way that we've been "sharing" top containers across multiple resources is with our microfilm reproductions of manuscript and archival collections. Our microfilm facsimiles and their corresponding manuscript/archival collections each have their own resource records in AS, with their own container instances. We wanted to link the microfilm instances (the use copies, at least) to archival objects in our manuscript/archival collections, so that our public services staff could tell (in Aeon) when a microfilm surrogate existed for a collection, and which archival objects were associated with which reels/boxes of film. Fortunately we had some legacy data about what was on each reel, which made it possible to programmatically determine which microfilm box to link with which archival object, and to create a relatively simple Python script to make those links in bulk via the API. I'd be happy to share that with you if you think it would be useful. The result is that we now have, for example, a single microfilm box that is represented as an instance of both a microfilm resource record and manuscript/archival resource record. The manuscript/archival resources that have been filmed have two instances listed for each archival object, one representing the box the original materials are in, and the other representing the microfilm box. And, when you view the top container, you can see linked records from both resources. Screenshots are attached. Hope this helps, and please let me know if you have any questions! Alicia Alicia Detelich Archivist Manuscripts and Archives Yale University Libraries 203-432-9893 alicia.detelich at yale.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Bowers, Kate A. Sent: Tuesday, July 11, 2017 12:26 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] "share" boxes / group boxes On Yale's (very helpful) web site http://guides.library.yale.edu/archivesspace/ASpaceContainerManagement there is this intriguing mention: The ability to "share" boxes across entire collections in a meaningful way. Let's say that you want to put all of the panoramic photos in your repository into the same container. With this new data model, you'll be able to keep much better control over that container. However, I've not been able to figure out how this ought to be done. Is anyone using AS to share boxes across multiple collections? If so, would you be willing to send a few screenshots or any documentation that you have? I'd be very grateful! Thanks, Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives kate_bowers at harvard.edu voice: (617) 998-5238 fax: (617) 495-8011 web: http://nrs.harvard.edu/urn-3:hul.eresource:archives Twitter: @k8_bowers -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ms_resource_2_instances.jpg Type: image/jpeg Size: 161031 bytes Desc: ms_resource_2_instances.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: top_container_view.jpg Type: image/jpeg Size: 159440 bytes Desc: top_container_view.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: microfilm_resource_instances.jpg Type: image/jpeg Size: 197112 bytes Desc: microfilm_resource_instances.jpg URL: From kate_bowers at harvard.edu Tue Jul 11 16:43:35 2017 From: kate_bowers at harvard.edu (Bowers, Kate A.) Date: Tue, 11 Jul 2017 20:43:35 +0000 Subject: [Archivesspace_Users_Group] "share" boxes / group boxes In-Reply-To: References: Message-ID: Thank you so much Mark and Alicia! Just what I needed! Kate From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Detelich, Alicia Sent: Tuesday, July 11, 2017 3:51 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] "share" boxes / group boxes Hi Kate, This use case may be slightly different than what you had in mind, but one way that we've been "sharing" top containers across multiple resources is with our microfilm reproductions of manuscript and archival collections. Our microfilm facsimiles and their corresponding manuscript/archival collections each have their own resource records in AS, with their own container instances. We wanted to link the microfilm instances (the use copies, at least) to archival objects in our manuscript/archival collections, so that our public services staff could tell (in Aeon) when a microfilm surrogate existed for a collection, and which archival objects were associated with which reels/boxes of film. Fortunately we had some legacy data about what was on each reel, which made it possible to programmatically determine which microfilm box to link with which archival object, and to create a relatively simple Python script to make those links in bulk via the API. I'd be happy to share that with you if you think it would be useful. The result is that we now have, for example, a single microfilm box that is represented as an instance of both a microfilm resource record and manuscript/archival resource record. The manuscript/archival resources that have been filmed have two instances listed for each archival object, one representing the box the original materials are in, and the other representing the microfilm box. And, when you view the top container, you can see linked records from both resources. Screenshots are attached. Hope this helps, and please let me know if you have any questions! Alicia Alicia Detelich Archivist Manuscripts and Archives Yale University Libraries 203-432-9893 alicia.detelich at yale.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Bowers, Kate A. Sent: Tuesday, July 11, 2017 12:26 PM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] "share" boxes / group boxes On Yale's (very helpful) web site http://guides.library.yale.edu/archivesspace/ASpaceContainerManagement there is this intriguing mention: The ability to "share" boxes across entire collections in a meaningful way. Let's say that you want to put all of the panoramic photos in your repository into the same container. With this new data model, you'll be able to keep much better control over that container. However, I've not been able to figure out how this ought to be done. Is anyone using AS to share boxes across multiple collections? If so, would you be willing to send a few screenshots or any documentation that you have? I'd be very grateful! Thanks, Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives kate_bowers at harvard.edu voice: (617) 998-5238 fax: (617) 495-8011 web: http://nrs.harvard.edu/urn-3:hul.eresource:archives Twitter: @k8_bowers -------------- next part -------------- An HTML attachment was scrubbed... URL: From livsolis at utexas.edu Wed Jul 12 07:07:32 2017 From: livsolis at utexas.edu (Olivia S Solis) Date: Wed, 12 Jul 2017 06:07:32 -0500 Subject: [Archivesspace_Users_Group] Advanced search, date label plugin? Message-ID: Hello all, Apologies if this is a newbie question, but I was wondering if anybody has developed an advanced search plugin in for searching date records via their labels (e.g. label="creation") that they might be willing to share. Our staff would very much appreciate this feature. I tend to learn by looking at examples. I have seen examples for newly developed plugins, but not for existing the default ArchivesSpace fields. I've also looked at the info here: http://archivesspace.github.io/archivesspace/user/archivesspace-plug-ins-readme/ but I'm not completely sure how you would refer to a field that is default in ":name" and ":solr_field". Thank you kindly! Olivia -- Olivia Solis, MSIS Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 -------------- next part -------------- An HTML attachment was scrubbed... URL: From trthorn2 at ncsu.edu Wed Jul 12 12:48:24 2017 From: trthorn2 at ncsu.edu (Trevor Thornton) Date: Wed, 12 Jul 2017 12:48:24 -0400 Subject: [Archivesspace_Users_Group] EAD3 export for ArchivesSpace being developed through a partnership of NC State and Duke In-Reply-To: References: Message-ID: For anyone interested in following the progress of the EAD3 export work on Github, here is the fork of ArchivesSpace I'm working from: https://github.com/NCSU-Libraries/archivesspace/tree/ead3_export There is a log at the top of the README with status updates. -Trevor On Thu, Jun 22, 2017 at 8:08 AM, Christine Di Bella < christine.dibella at lyrasis.org> wrote: > Hello ArchivesSpace members, > > > > I?m pleased to announce that community members Trevor Thornton of North > Carolina State University and Noah Huffman of Duke University are taking > the lead this summer on building an exporter that will provide a first > level of EAD3 support in the ArchivesSpace application. Trevor will be > doing the development and Noah will be providing leadership and guidance > from the functional side of things. > > > > Their work will be based on the mapping for EAD3 that the Migrations > sub-team of our Technical Advisory Council circulated in the community > earlier this year. The initial focus is on ArchivesSpace being able to > export valid EAD3. Building on this work, the program will continue to > consider how to provide additional levels of support ? with help in this > area always much appreciated. > > > > As work proceeds, you will be able to comment on and track progress in the > JIRA issue: https://archivesspace.atlassian.net/browse/AR-923. The > guiding principles and mapping being used for the project are linked from > the comments on the issue. We?ll post more links, including to the Github > repository for the developing code, as work progresses. > > > > For questions about the EAD3 exporter project, please contact Noah ( > noah.huffman at duke.edu) or Trevor (trthorn2 at ncsu.edu). For questions or > ideas about EAD3 support overall, feel free to post to the JIRA issue or > get in touch with me. > > > > Thanks to Trevor and Noah and their institutions for their generosity in > taking on this project. If you or your institution are interested in > getting more involved in development for ArchivesSpace, and either have > projects in mind or want to know about projects already prioritized by the > community, please get in touch with Laney or me. We?d love to hear from you! > > > > Christine > > > > Christine Di Bella > > ArchivesSpace Program Manager > > christine.dibella at lyrasis.org > > 800.999.8558 x2905 <(800)%20999-8558> > > 678-235-2905 <(678)%20235-2905> > > cdibella13 (Skype) > > > > [image: ASpaceOrgHomeMedium] > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Trevor Thornton Applications Developer, Digital Library Initiatives North Carolina State University Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 13904 bytes Desc: not available URL: From AikensB at si.edu Wed Jul 12 13:38:05 2017 From: AikensB at si.edu (Aikens, Barbara) Date: Wed, 12 Jul 2017 17:38:05 +0000 Subject: [Archivesspace_Users_Group] Appraisal plug-in In-Reply-To: References: , Message-ID: <9EC2AA21B357BB459D3CBE9AC3FD821551ABC5D3@si-msedag04.US.SINET.SI.EDU> Dear Brian, I understand that an archival assessment plug-in is currently under development by Tufts that will include rating values for physical condition, physical "access", research value, intellectual access, and condition of housing - all primary components of archival appraisal. Essentially, this new plug-in will be similar to the AT Assessment Module, with added reporting capabilities. If it mirrors the AT module, there should be user-defined fields and note fields also available. Barbara Aikens, Retired ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org [archivesspace_users_group-bounces at lyralists.lyrasis.org] on behalf of Brian Thomas [bthomas at tsl.texas.gov] Sent: Friday, June 23, 2017 9:54 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Appraisal plug-in I was referring to an archival appraisal plug-in. We are not worried at the moment about valuation, and unfortunately the appraisal/de-accession events do not allow the level of detail we are seeking. Thanks for the reply Brian From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Olivia S Solis Sent: Friday, June 23, 2017 8:16 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Appraisal plug-in Hi Brian, For clarification, do you mean a monetary appraisal or an archival appraisal? We are interested in representing monetary appraisals in ASpace. For now we decided to document the info in the "Appraisal" event. It would be nice to be able to document monetary value in an easily searchable way, though. Thanks, Olivia On Thu, Jun 22, 2017 at 9:36 AM, Brian Thomas > wrote: We are considering appraisal reports for our implementation of AS and were wondering if anyone is using a plug-in to handle this type of thing? I didn?t see anything in the plug-ins on the wiki. The User Defined fields will work, but if someone has something better? Brian Thomas Electronic Records Specialist Texas State Library and Archives Commission 1201 Brazos Street Austin, TX 78701 PH: (512) 475-3374 e-mail: bthomas at tsl.texas.gov tsl.texas.gov [cid:image001.jpg at 01D029A2.37194C70] _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Olivia Solis, MSIS Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5314 bytes Desc: image001.png URL: From bthomas at tsl.texas.gov Wed Jul 12 13:40:57 2017 From: bthomas at tsl.texas.gov (Brian Thomas) Date: Wed, 12 Jul 2017 17:40:57 +0000 Subject: [Archivesspace_Users_Group] Appraisal plug-in In-Reply-To: <9EC2AA21B357BB459D3CBE9AC3FD821551ABC5D3@si-msedag04.US.SINET.SI.EDU> References: , <9EC2AA21B357BB459D3CBE9AC3FD821551ABC5D3@si-msedag04.US.SINET.SI.EDU> Message-ID: Thank you, I will keep my eye out for it. Brian From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Aikens, Barbara Sent: Wednesday, July 12, 2017 12:38 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Appraisal plug-in Dear Brian, I understand that an archival assessment plug-in is currently under development by Tufts that will include rating values for physical condition, physical "access", research value, intellectual access, and condition of housing - all primary components of archival appraisal. Essentially, this new plug-in will be similar to the AT Assessment Module, with added reporting capabilities. If it mirrors the AT module, there should be user-defined fields and note fields also available. Barbara Aikens, Retired ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org [archivesspace_users_group-bounces at lyralists.lyrasis.org] on behalf of Brian Thomas [bthomas at tsl.texas.gov] Sent: Friday, June 23, 2017 9:54 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Appraisal plug-in I was referring to an archival appraisal plug-in. We are not worried at the moment about valuation, and unfortunately the appraisal/de-accession events do not allow the level of detail we are seeking. Thanks for the reply Brian From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Olivia S Solis Sent: Friday, June 23, 2017 8:16 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Appraisal plug-in Hi Brian, For clarification, do you mean a monetary appraisal or an archival appraisal? We are interested in representing monetary appraisals in ASpace. For now we decided to document the info in the "Appraisal" event. It would be nice to be able to document monetary value in an easily searchable way, though. Thanks, Olivia On Thu, Jun 22, 2017 at 9:36 AM, Brian Thomas > wrote: We are considering appraisal reports for our implementation of AS and were wondering if anyone is using a plug-in to handle this type of thing? I didn't see anything in the plug-ins on the wiki. The User Defined fields will work, but if someone has something better... Brian Thomas Electronic Records Specialist Texas State Library and Archives Commission 1201 Brazos Street Austin, TX 78701 PH: (512) 475-3374 e-mail: bthomas at tsl.texas.gov tsl.texas.gov [cid:image001.jpg at 01D029A2.37194C70] _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Olivia Solis, MSIS Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5314 bytes Desc: image001.png URL: From bmg17 at psu.edu Wed Jul 12 19:18:49 2017 From: bmg17 at psu.edu (Ben Goldman) Date: Wed, 12 Jul 2017 19:18:49 -0400 (EDT) Subject: [Archivesspace_Users_Group] Encoding instances without containers Message-ID: <1928743857.1401700.1499901529433.JavaMail.zimbra@psu.edu> Hi Everyone, Having just recently upgraded to a post 1.5 world, we're learning more about the top container functionality. One immediate thing we noticed is that we cannot assign child indicators without creating or linking to a top container record. Which makes sense. But I'm curious to know how other institutions go about identifying locations for material not housed in a container, such as ledgers or artifacts? Thanks, Ben Ben Goldman Digital Records Archivist & Sally W. Kalin Early Career Librarian for Technological Innovations Penn State University Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: From EJOLLEY at nla.gov.au Wed Jul 12 19:21:33 2017 From: EJOLLEY at nla.gov.au (Emma Jolley) Date: Wed, 12 Jul 2017 23:21:33 +0000 Subject: [Archivesspace_Users_Group] Encoding instances without containers In-Reply-To: <1928743857.1401700.1499901529433.JavaMail.zimbra@psu.edu> References: <1928743857.1401700.1499901529433.JavaMail.zimbra@psu.edu> Message-ID: <81FF938BA2407B4DA1E134E7FA5C09EC025BB8ED3C@EXMBX2.shire.nla.gov.au> Hi Ben At the National Library of Australia we make the shelf on which the volume sits a ?Top Container?? Emma Emma Jolley| Curator of Digital Archives, Pictures and Manuscripts Branch|National Library of Australia Canberra ACT 2600 e: emma.jolley at nla.gov.au|t: 02 6262 1456| www.nla.gov.au/ms http://www.nla.gov.au/support-us/make-a-collection-offer-pictures-and-manuscripts From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Ben Goldman Sent: Thursday, 13 July 2017 9:19 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Encoding instances without containers Hi Everyone, Having just recently upgraded to a post 1.5 world, we're learning more about the top container functionality. One immediate thing we noticed is that we cannot assign child indicators without creating or linking to a top container record. Which makes sense. But I'm curious to know how other institutions go about identifying locations for material not housed in a container, such as ledgers or artifacts? Thanks, Ben Ben Goldman Digital Records Archivist & Sally W. Kalin Early Career Librarian for Technological Innovations Penn State University Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: From EJOLLEY at nla.gov.au Wed Jul 12 21:46:24 2017 From: EJOLLEY at nla.gov.au (Emma Jolley) Date: Thu, 13 Jul 2017 01:46:24 +0000 Subject: [Archivesspace_Users_Group] Manage Top Container Message-ID: <81FF938BA2407B4DA1E134E7FA5C09EC025BB8EDF7@EXMBX2.shire.nla.gov.au> Hi All We have noticed that in the Manage Top Containers view - when we have multiple Collections sharing a single Top Container - that the Series number that populates is from the First Collection - this is misleading when a retriever is trying to find a Series number for another Collection in the Top Container (see image attached) - am I doing something wrong or is this a known bug.... It would be easier in this case not to have the Series number at all or to have all of the Series numbers. Many thanks for the advice as always. Emma Emma Jolley| Curator of Digital Archives, Pictures and Manuscripts Branch|National Library of Australia Canberra ACT 2600 e: emma.jolley at nla.gov.au|t: 02 6262 1456| www.nla.gov.au/ms http://www.nla.gov.au/support-us/make-a-collection-offer-pictures-and-manuscripts -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Capture.PNG Type: image/png Size: 149715 bytes Desc: Capture.PNG URL: From kate_bowers at harvard.edu Thu Jul 13 08:55:08 2017 From: kate_bowers at harvard.edu (Bowers, Kate A.) Date: Thu, 13 Jul 2017 12:55:08 +0000 Subject: [Archivesspace_Users_Group] Encoding instances without containers In-Reply-To: <1928743857.1401700.1499901529433.JavaMail.zimbra@psu.edu> References: <1928743857.1401700.1499901529433.JavaMail.zimbra@psu.edu> Message-ID: While we have not yet implemented container management in AS, we are looking very hard at how we might do so, and so examining the business model in AS very closely and comparing it to our current locations and container management database, so I am really glad to see your question! At the Harvard University Archives every such item is a "unit" (our term) and receives an identifying number as if it were a "top container" (AS term). Thus it can be tracked and moved and associated with physical locations and fulfillment requests just as if it were any other box. If you do this in AS and create a no-container "container profiles" -- which would be a great way to find those that are more vulnerable because they are not boxed anyway -- I hope you report back on whether or not this works for you! Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives kate_bowers at harvard.edu 617.496.2713 voice: (617) 998-5238 fax: (617) 495-8011 web: http://nrs.harvard.edu/urn-3:hul.eresource:archives Twitter: @k8_bowers ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Ben Goldman Sent: Wednesday, July 12, 2017 7:18 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Encoding instances without containers Hi Everyone, Having just recently upgraded to a post 1.5 world, we're learning more about the top container functionality. One immediate thing we noticed is that we cannot assign child indicators without creating or linking to a top container record. Which makes sense. But I'm curious to know how other institutions go about identifying locations for material not housed in a container, such as ledgers or artifacts? Thanks, Ben Ben Goldman Digital Records Archivist & Sally W. Kalin Early Career Librarian for Technological Innovations Penn State University Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: From adrien_hilton at harvard.edu Thu Jul 13 09:11:47 2017 From: adrien_hilton at harvard.edu (Hilton, Adrien) Date: Thu, 13 Jul 2017 13:11:47 +0000 Subject: [Archivesspace_Users_Group] Encoding instances without containers In-Reply-To: References: <1928743857.1401700.1499901529433.JavaMail.zimbra@psu.edu> Message-ID: Hi Ben and Kate, We're making everything that can/will circulate a Top Container. We have a number of collections with volumes on a shelf. We're marking them as Top Container Type "Volume" and Container Indicator "1" "2" and so on. Same thing for folders in a flat file. The flat file and drawer are locations (because they don't circulate) but the folder that will circulate would be Top Container Type "Folder" and Container Instance "1" "2" and so on. Would the same work for artifact or ledger? Best wishes, Adrien From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Bowers, Kate A. Sent: Thursday, July 13, 2017 8:55 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Encoding instances without containers While we have not yet implemented container management in AS, we are looking very hard at how we might do so, and so examining the business model in AS very closely and comparing it to our current locations and container management database, so I am really glad to see your question! At the Harvard University Archives every such item is a "unit" (our term) and receives an identifying number as if it were a "top container" (AS term). Thus it can be tracked and moved and associated with physical locations and fulfillment requests just as if it were any other box. If you do this in AS and create a no-container "container profiles" -- which would be a great way to find those that are more vulnerable because they are not boxed anyway -- I hope you report back on whether or not this works for you! Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives kate_bowers at harvard.edu 617.496.2713 voice: (617) 998-5238 fax: (617) 495-8011 web: http://nrs.harvard.edu/urn-3:hul.eresource:archives Twitter: @k8_bowers ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Ben Goldman > Sent: Wednesday, July 12, 2017 7:18 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Encoding instances without containers Hi Everyone, Having just recently upgraded to a post 1.5 world, we're learning more about the top container functionality. One immediate thing we noticed is that we cannot assign child indicators without creating or linking to a top container record. Which makes sense. But I'm curious to know how other institutions go about identifying locations for material not housed in a container, such as ledgers or artifacts? Thanks, Ben Ben Goldman Digital Records Archivist & Sally W. Kalin Early Career Librarian for Technological Innovations Penn State University Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: From cspeterson at email.gwu.edu Thu Jul 13 10:06:35 2017 From: cspeterson at email.gwu.edu (Peterson, Christie) Date: Thu, 13 Jul 2017 10:06:35 -0400 Subject: [Archivesspace_Users_Group] Encoding instances without containers In-Reply-To: References: <1928743857.1401700.1499901529433.JavaMail.zimbra@psu.edu> Message-ID: Here at GW, we are actively in the process of migrating from 1.4.3 to 1.5 (i.e., to top containers) and our goal is for non-boxed volumes and artifacts to be their own top containers, as Adrien and Kate have suggested. I'm curious if there was some reason why you didn't want to go that route? Something that maybe we haven't considered? -- Christie S. Peterson University Archivist George Washington University Libraries 704H Gelman Library cspeterson at gwu.edu 202.994.3925 -------------- next part -------------- An HTML attachment was scrubbed... URL: From EJOLLEY at nla.gov.au Thu Jul 13 21:58:46 2017 From: EJOLLEY at nla.gov.au (Emma Jolley) Date: Fri, 14 Jul 2017 01:58:46 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace bug report - use of & Message-ID: <81FF938BA2407B4DA1E134E7FA5C09EC025BBA02B3@EXMBX1.shire.nla.gov.au> Hi We have had a persistent issue with the export of the '&' character in EAD XML - we can get around it by using the encoding term "&" instead of &. The issues is currently causing an problem with the synchronisation between ArchivesSpace and Preservica and is further explained in the email below. It would be great if this issue could be fixed in the next release? Please let me know if you'd like me to log this in formal system (JIRA?) Many thanks Emma Emma Jolley| Curator of Digital Archives, Pictures and Manuscripts Branch|National Library of Australia Canberra ACT 2600 e: emma.jolley at nla.gov.au|t: 02 6262 1456| www.nla.gov.au/ms http://www.nla.gov.au/support-us/make-a-collection-offer-pictures-and-manuscripts From: Ninh Nguyen (IT) Sent: Friday, 14 July 2017 10:51 AM To: Emma Jolley > Cc: Rachael Eddowes >; Ninh Nguyen (IT) >; Kavinga Hubert >; Shaun Coen > Subject: ArchivesSpace bug report Hi Emma, During the Preservica ArchicesSpace synchronisation testing, I think we've found a bug with the ArchivesSpace export to EAD module. I believe you are the contact person for ArchivesSpace? Can I pass this bug report to you to pass on to the ArchivesSpace people? Or should I contact ArchivesSpace directly by some means? The bug was discovered when we tested the sync, but it doesn't relate to the Preservica sync. Any user can create the bug by editing some fields in ArchivesSpace. And the bug is: ArchivesSpace allows some fields to store html code. For example, following a sync, the following html code is store in the Sub Notes field of an 'Other Finding Aids' Notes field. http://tallis.nla.gov.au:8080/resources/3644#tree::resource_3644 Preservica Internal When the collection is exported to EAD in xml, ArchivesSpace escaped characters inside the href to make the xml well-formed. The above will turn into a correct form (0a5b4e7f-5fbe-4f99-832a-d69e0b5302b7 is the Preservica UUID) Preservica Internal However, if the UUID starts with character 'a', for some reason the export won't escape the ampersand, eg. http://tallis.nla.gov.au:8080/resources/3646#tree::resource_3646 won't turn & to & and it makes the EAD xml not well-formed. You can test it by creating a new record, and adding some html code (with &) in some fields before exporting it to EAD. I've tested it in ArchivesSpace 1.5.4 as well as the latest version 2.0.0 and the results are the same. Could you pass it to the ArchivesSpace people, or let me know how to report it? Thanks, Ninh -------------- next part -------------- An HTML attachment was scrubbed... URL: From kayla.skillin at boston.gov Fri Jul 14 14:50:00 2017 From: kayla.skillin at boston.gov (Kayla Skillin) Date: Fri, 14 Jul 2017 14:50:00 -0400 Subject: [Archivesspace_Users_Group] Finding aid stylesheet Message-ID: Hello, We have been updating a lot of our finding aids to add to our website and noticed that the stylesheet might have changed since the upgrade. For instance, the date labels are now appearing on every record in the finding aid twice, once with normally after the title and also underneath the item with a date label, and we would like to have that taken out. (example below): [image: Inline image 1] Is this something that needs to be customized or can it be easily changed? Thanks, Kayla [image: Digital_City_Seal_black.png] Kayla Skillin Assistant Archivist City of Boston Archives 617.635.1195 <(617)%20635-1195> (w) -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 11802 bytes Desc: not available URL: From bmg17 at psu.edu Fri Jul 14 14:58:10 2017 From: bmg17 at psu.edu (Ben Goldman) Date: Fri, 14 Jul 2017 14:58:10 -0400 (EDT) Subject: [Archivesspace_Users_Group] Encoding instances without containers In-Reply-To: References: <1928743857.1401700.1499901529433.JavaMail.zimbra@psu.edu> Message-ID: <1074556433.3981207.1500058690305.JavaMail.zimbra@psu.edu> Thanks to everyone for sharing some of their approaches to encoding top containers. It's been very helpful for us in working through local scenarios. Best Regards, Ben Ben Goldman Digital Records Archivist & Sally W. Kalin Early Career Librarian for Technological Innovations Penn State University Libraries From: "Peterson, Christie" To: "Archivesspace Users Group" Sent: Thursday, July 13, 2017 10:06:35 AM Subject: Re: [Archivesspace_Users_Group] Encoding instances without containers Here at GW, we are actively in the process of migrating from 1.4.3 to 1.5 (i.e., to top containers) and our goal is for non-boxed volumes and artifacts to be their own top containers, as Adrien and Kate have suggested. I'm curious if there was some reason why you didn't want to go that route? Something that maybe we haven't considered? -- Christie S. Peterson University Archivist George Washington University Libraries 704H Gelman Library [ mailto:cspeterson at gwu.edu | cspeterson at gwu.edu ] 202.994.3925 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From bobbi_fox at harvard.edu Fri Jul 14 15:43:54 2017 From: bobbi_fox at harvard.edu (Fox, Bobbi) Date: Fri, 14 Jul 2017 19:43:54 +0000 Subject: [Archivesspace_Users_Group] A plugin to support bulk uploading of Archival Objects via Excel Spreadsheet Message-ID: Library Technology Services, which supports the Harvard Library, is pleased to announce the availability of a new plugin, aspace-import-excel, available on GitHub at https://github.com/harvard-library/aspace-import-excel . Using the provided spreadsheet template, users can go to a Resource, and either add or insert the set of Archival Objects that have been defined in the spreadsheet. Please note carefully the following paragraph in the README: The intention is not to completely reproduce a Finding Aid as presented in an EAD XML, or to allow for every permutation of Archival Object creation within ArchivesSpace. We are aiming for the "80% rule"; that is, at least 80% of the work that would be done interactively can be replaced by an excel spreadsheet; additional refinements to individual archival objects (such as addition of agents-as-subjects, assignment of locations to top-level containers, etc.) would take place interactively. Installation information is on the main README file, with User Documentation at https://github.com/harvard-library/aspace-import-excel/blob/master/user_documentation/USER_DOCUMENTATION.md , including workflow, step by step usage, and extensive (exhaustive? :-) explanation of the Spreadsheet Template. This plugin was designed to aid the Harvard Library archival community, but we hope that it may be useful to other archivists in the ArchivesSpace community. Pull requests welcome. If you encounter problems, please create an issue on the GitHub repository. Cheers, Bobbi Fox, Maintainer -------------- next part -------------- An HTML attachment was scrubbed... URL: From VivianLea.Solek at Kofc.Org Fri Jul 14 15:57:20 2017 From: VivianLea.Solek at Kofc.Org (VivianLea.Solek at Kofc.Org) Date: Fri, 14 Jul 2017 15:57:20 -0400 Subject: [Archivesspace_Users_Group] A plugin to support bulk uploading of Archival Objects via Excel Spreadsheet In-Reply-To: References: Message-ID: Hi Bobbi, ...so this would get our raw data from Excel into ASpace without going through an EAD transformation? I'm migrating from an ANCIENT DOS system which I've been able to get out to excel. Once I have that cleaned up, if I and my IT partner can skip the transformation step, that would be beyond fabulous! There are only 15 fields to come over, so it would be very easy to map them to your template. Looking forward to your response, which might make my whole month! All the best, VivianLea VivianLea Solek Archivist Knights of Columbus Supreme Council Archives Knights of Columbus Museum 1 State Street New Haven, CT 06511-6702 Phone 203 752-4578 Fax 203 865-0351 From: "Fox, Bobbi" To: "archivesspace_users_group at lyralists.lyrasis.org" , Date: 07/14/2017 03:44 PM Subject: [Archivesspace_Users_Group] A plugin to support bulk uploading of Archival Objects via Excel Spreadsheet Sent by: archivesspace_users_group-bounces at lyralists.lyrasis.org Library Technology Services, which supports the Harvard Library, is pleased to announce the availability of a new plugin, aspace-import-excel, available on GitHub at https://github.com/harvard-library/aspace-import-excel . Using the provided spreadsheet template, users can go to a Resource, and either add or insert the set of Archival Objects that have been defined in the spreadsheet. Please note carefully the following paragraph in the README: The intention is not to completely reproduce a Finding Aid as presented in an EAD XML, or to allow for every permutation of Archival Object creation within ArchivesSpace. We are aiming for the "80% rule"; that is, at least 80% of the work that would be done interactively can be replaced by an excel spreadsheet; additional refinements to individual archival objects (such as addition of agents-as-subjects, assignment of locations to top-level containers, etc.) would take place interactively. Installation information is on the main README file, with User Documentation at https://github.com/harvard-library/aspace-import-excel/blob/master/user_documentation/USER_DOCUMENTATION.md , including workflow, step by step usage, and extensive (exhaustive? :-) explanation of the Spreadsheet Template. This plugin was designed to aid the Harvard Library archival community, but we hope that it may be useful to other archivists in the ArchivesSpace community. Pull requests welcome. If you encounter problems, please create an issue on the GitHub repository. Cheers, Bobbi Fox, Maintainer _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=CwICAg&c=C90XguLnqhMT2ADRaOs3gQ&r=balEICFvGrVJ8Sr6vcdFtVtZaJWT42A5myJ4zXSQILc&m=GXMnvtV2cyS8rDYQOUdBae-J3_5pKCeySUAi9E3PwPI&s=x7wbsF-0e7H4tdAqlZfuP-j27pCXO_i_JOAwg51LQMs&e= CONFIDENTIALITY NOTICE: This message and any attachments may contain confidential, proprietary or legally privileged information and is intended only for the use of the addressee or addressees named above for its intended purpose. If you are not the intended recipient of this message, this message constitutes notice that any review, retransmission, distribution, copying or other use or taking any action in reliance on the information in this message and its attachments, is prohibited. If you receive this communication in error, please immediately advise the sender by reply e-mail and delete this message and its attachments from your system without keeping a copy. Unless expressly stated in this e-mail, nothing in this message may be construed as a digital or electronic signature. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: graycol.gif Type: image/gif Size: 105 bytes Desc: not available URL: From bobbi_fox at harvard.edu Fri Jul 14 16:00:16 2017 From: bobbi_fox at harvard.edu (Fox, Bobbi) Date: Fri, 14 Jul 2017 20:00:16 +0000 Subject: [Archivesspace_Users_Group] A plugin to support bulk uploading of Archival Objects via Excel Spreadsheet In-Reply-To: References: Message-ID: Hi, VivianLea, Take a look at the template, and see if it meets your needs; you do, however, have to create the Resource, however minimally, in ArchivesSpace somehow (could be interactively, of course!) Cheers, Bobbi From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of VivianLea.Solek at Kofc.Org Sent: Friday, July 14, 2017 3:57 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] A plugin to support bulk uploading of Archival Objects via Excel Spreadsheet Hi Bobbi, ...so this would get our raw data from Excel into ASpace without going through an EAD transformation? I'm migrating from an ANCIENT DOS system which I've been able to get out to excel. Once I have that cleaned up, if I and my IT partner can skip the transformation step, that would be beyond fabulous! There are only 15 fields to come over, so it would be very easy to map them to your template. Looking forward to your response, which might make my whole month! All the best, VivianLea VivianLea Solek Archivist Knights of Columbus Supreme Council Archives Knights of Columbus Museum 1 State Street New Haven, CT 06511-6702 Phone 203 752-4578 Fax 203 865-0351 [Inactive hide details for "Fox, Bobbi" ---07/14/2017 03:44:00 PM---Library Technology Services, which supports the Harvard Libr]"Fox, Bobbi" ---07/14/2017 03:44:00 PM---Library Technology Services, which supports the Harvard Library, is pleased to announce the availabi From: "Fox, Bobbi" > To: "archivesspace_users_group at lyralists.lyrasis.org" >, Date: 07/14/2017 03:44 PM Subject: [Archivesspace_Users_Group] A plugin to support bulk uploading of Archival Objects via Excel Spreadsheet Sent by: archivesspace_users_group-bounces at lyralists.lyrasis.org ________________________________ Library Technology Services, which supports the Harvard Library, is pleased to announce the availability of a new plugin, aspace-import-excel, available on GitHub at https://github.com/harvard-library/aspace-import-excel . Using the provided spreadsheet template, users can go to a Resource, and either add or insert the set of Archival Objects that have been defined in the spreadsheet. Please note carefully the following paragraph in the README: The intention is not to completely reproduce a Finding Aid as presented in an EAD XML, or to allow for every permutation of Archival Object creation within ArchivesSpace. We are aiming for the "80% rule"; that is, at least 80% of the work that would be done interactively can be replaced by an excel spreadsheet; additional refinements to individual archival objects (such as addition of agents-as-subjects, assignment of locations to top-level containers, etc.) would take place interactively. Installation information is on the main README file, with User Documentation at https://github.com/harvard-library/aspace-import-excel/blob/master/user_documentation/USER_DOCUMENTATION.md , including workflow, step by step usage, and extensive (exhaustive? :-) explanation of the Spreadsheet Template. This plugin was designed to aid the Harvard Library archival community, but we hope that it may be useful to other archivists in the ArchivesSpace community. Pull requests welcome. If you encounter problems, please create an issue on the GitHub repository. Cheers, Bobbi Fox, Maintainer _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=CwICAg&c=C90XguLnqhMT2ADRaOs3gQ&r=balEICFvGrVJ8Sr6vcdFtVtZaJWT42A5myJ4zXSQILc&m=GXMnvtV2cyS8rDYQOUdBae-J3_5pKCeySUAi9E3PwPI&s=x7wbsF-0e7H4tdAqlZfuP-j27pCXO_i_JOAwg51LQMs&e= CONFIDENTIALITY NOTICE: This message and any attachments may contain confidential, proprietary or legally privileged information and is intended only for the use of the addressee or addressees named above for its intended purpose. If you are not the intended recipient of this message, this message constitutes notice that any review, retransmission, distribution, copying or other use or taking any action in reliance on the information in this message and its attachments, is prohibited. If you receive this communication in error, please immediately advise the sender by reply e-mail and delete this message and its attachments from your system without keeping a copy. Unless expressly stated in this e-mail, nothing in this message may be construed as a digital or electronic signature. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 105 bytes Desc: image001.gif URL: From alexanderduryee at nypl.org Fri Jul 14 17:12:55 2017 From: alexanderduryee at nypl.org (Alexander Duryee) Date: Fri, 14 Jul 2017 17:12:55 -0400 Subject: [Archivesspace_Users_Group] Barcodes Disappearing from Database Message-ID: We've started assigning barcodes in bulk via the Manage Top Containers screen, and have run into a troubling issue. Assigning barcodes to Top Containers via the Rapid Barcode Entry screen has gone well; however, ranges of barcodes (typically the last set done at once) will disappear from the application without warning. Examining the system log reveals that the barcodes were not removed via the frontend or API - there are no API calls that would have assigned a blank value to the containers. More perplexing, the missing barcodes do not manifest in the index - searching the barcodes via the Manage Top Container screen would show them as being present, but checking the container directly (or the backend database) shows no barcode. It's as if the data simply disappeared, with no obvious cause. NYPL has created a number of custom plugins, so it's not impossible that one of them is causing the issue. However, none of our plugins directly modify the TopContainer model, so I doubt that one of them is causing the issue. We're on 1.5.1 still. Has anyone else encountered an issue like this, or is there something I should be on the lookout for that could be impacting our data? Thanks! --Alex -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderduryee at nypl.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From carrie.daniels at louisville.edu Mon Jul 17 10:27:11 2017 From: carrie.daniels at louisville.edu (carrie.daniels at louisville.edu) Date: Mon, 17 Jul 2017 14:27:11 +0000 Subject: [Archivesspace_Users_Group] Problem with Classifications: searching/adding to records Message-ID: We have been having a problem with Classifications for quite some time - we are currently in version 1.5.2, but I think the issue actually predates our move to 1.5.2 and it's just finally gotten exasperating. And we did some testing on 2.1.0-RC1, and it persists. In our workflow, every Accession and Resource record is assigned a Classification. When adding a Classification to the Accession/Resource record, AS takes a long time to search/find Classifications, particularly the one with (by far) the most records associated with it (about 3300). Saving is also very slow (slow enough that the browser can tell us as the percentage uploaded increases). We've monitored the system while going through these processes, and Java is working overtime during the search process. Has anyone else seen this? And/or have ideas as to how we can fix it? Thanks! Carrie Carrie Daniels University Archivist and Director, Archives and Special Collections University of Louisville -------------- next part -------------- An HTML attachment was scrubbed... URL: From gpgaidmore at wm.edu Mon Jul 17 19:02:43 2017 From: gpgaidmore at wm.edu (Gaidmore, Gerald) Date: Mon, 17 Jul 2017 23:02:43 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace election results and new appointments Message-ID: To the members of the ArchivesSpace community: I am pleased to announce the results of the elections we recently conducted to fill vacancies on the ArchivesSpace Governance Board. * Gordon Daines, Special Collections Department Chair, at Brigham Young University, has been elected to serve as the representative for Large member institutions * Peter Carini, College Archivist, at Dartmouth College, has been elected to serve as the representative for Medium member institution. * Nicholas Zmijewski, Archivist, at the Industrial Archives and Library in Bethlehem, Pennsylvania, has been elected to serve as the representative for Very Small member institution. Gordon, Peter, and Nick will serve two-year terms, effective from July 1, 2017, and running through June 30, 2019. We extend our renewed thanks to outgoing representatives Christian Dupont (Boston College), Jay Gaidmore (College of William & Mary), and Tom Adams (Cold Spring Harbor Laboratory). We remain grateful to Christian Dupont, Ann Hodges, and Tom Adams for their candidacies. We also want to thank Johna Von Behrens (University of Louisiana Lafayette), Cyndi Shein (UNLV), Mary Saffell (Texas Christian University), Julia Novakovic (The Strong National Museum of Play), and Annie Tummino (SUNY Maritime) for their service on the 2017 Nominating Committee. The leadership needs of our community-based, community-driven organization are ongoing, and so the contributions of all members, including those of you who voted as voting representatives for your member institutions, continue to be greatly valued. The board has also recently approved the appointments of six new members to the Technical Services Advisory Council: Bobbi Fox (Harvard University), Trevor Thornton (North Carolina State University), Maggie Hughes (UCLA), Dallas Pillen (University of Michigan), Julia McGinnis (California University of Pennsylvania), Megan Blair (St. Edward's University), as well as four new members of the User Services Advisory Council: Brittany Newberry (Atlanta University Center); Alston Cobourn (Texas A&M - Corpus Christi); Scott Ziegler (American Philosophical Society); Ann Merryman (University of South Carolina Upstate). Best wishes to all as we welcome our representatives to their new roles and look ahead to coming year. Respectfully submitted, Jay Jay Gaidmore 2017 Nominating Committee Chair College of William & Mary -------------- next part -------------- An HTML attachment was scrubbed... URL: From KUTZUBA at hws.edu Tue Jul 18 09:55:36 2017 From: KUTZUBA at hws.edu (Kutzuba, Jamie) Date: Tue, 18 Jul 2017 13:55:36 +0000 Subject: [Archivesspace_Users_Group] Upgrade from 1.3 to 1.5.2 - data issues Message-ID: <47bd0c0eac3942c8a2001f3787f04b5e@EXCH13MBX1.hws.edu> Hello- I upgraded our instance from 1.3.0 to 1.5.2 yesterday in order to move to 2.0. I can run archivesspace.bat and bring up the public and staff interfaces but the staff side is not showing any of the data. On the public side there is no browseable data. Searching on either interface will bring up the archival components (lower-down levels of a finding aid, like each file or item) but not the resource records themselves (collection-level records). If I click on an archival component it does bring me to its resource record, so the resources are still there, but they are not showing up in the searches nor in the browse section. Did the conversion go awry? Would it be best to roll back or is there something else I can do to resolve this? Running Windows Server 2012 R2, MySQL 5.6. Thanks for your help- Jamie Jamie Kutzuba Systems Librarian 315.781.4355 Warren Hunting Smith Library Hobart & William Smith Colleges -------------- next part -------------- An HTML attachment was scrubbed... URL: From clobdel1 at swarthmore.edu Tue Jul 18 10:25:03 2017 From: clobdel1 at swarthmore.edu (Chelsea Lobdell) Date: Tue, 18 Jul 2017 10:25:03 -0400 Subject: [Archivesspace_Users_Group] Upgrade from 1.3 to 1.5.2 - data issues In-Reply-To: <47bd0c0eac3942c8a2001f3787f04b5e@EXCH13MBX1.hws.edu> References: <47bd0c0eac3942c8a2001f3787f04b5e@EXCH13MBX1.hws.edu> Message-ID: Hi Jamie, TriCo Libraries recently experienced issues with search and browse after a migration from v1.5.3 to v2.0.1. It is possible for the Solr index to get messed up during an upgrade. Below is what Lyrasis recommended I do as a first step. It basically removes all old index data and forces an entire re-index. stop archivesspace back up /path/to/archivespace/data/ just in case (cp -a /path/to/archivespace/data/ /path/to/someplace/safe/) rm -rf /path/to/archivespace/data/* start archivesspace up again I suggest trying that and seeing if it helps. - Chelsea *---------------* *Chelsea Lobdell* *Library Web Developer/ Swarthmore College* *clobdel1 at swarthmore.edu / (610)690-6818* On Tue, Jul 18, 2017 at 9:55 AM, Kutzuba, Jamie wrote: > Hello- > > > > I upgraded our instance from 1.3.0 to 1.5.2 yesterday in order to move to > 2.0. I can run archivesspace.bat and bring up the public and staff > interfaces but the staff side is not showing any of the data. On the public > side there is no browseable data. Searching on either interface will bring > up the archival components (lower-down levels of a finding aid, like each > file or item) but not the resource records themselves (collection-level > records). If I click on an archival component it does bring me to its > resource record, so the resources are still there, but they are not showing > up in the searches nor in the browse section. > > > > Did the conversion go awry? Would it be best to roll back or is there > something else I can do to resolve this? > > > > Running Windows Server 2012 R2, MySQL 5.6. > > > > Thanks for your help- Jamie > > > > *Jamie Kutzuba* > > Systems Librarian > > 315.781.4355 <(315)%20781-4355> > > Warren Hunting Smith Library > > Hobart & William Smith Colleges > > > > > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From KUTZUBA at hws.edu Tue Jul 18 11:03:44 2017 From: KUTZUBA at hws.edu (Kutzuba, Jamie) Date: Tue, 18 Jul 2017 15:03:44 +0000 Subject: [Archivesspace_Users_Group] Upgrade from 1.3 to 1.5.2 - data issues In-Reply-To: References: <47bd0c0eac3942c8a2001f3787f04b5e@EXCH13MBX1.hws.edu> Message-ID: <785d8e5652c540a882193f63f0dcbaa2@EXCH13MBX1.hws.edu> Hi Chelsea- Thanks. I?m giving that a go now. - Jamie 315.781.4355 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chelsea Lobdell Sent: Tuesday, July 18, 2017 10:25 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Upgrade from 1.3 to 1.5.2 - data issues Hi Jamie, TriCo Libraries recently experienced issues with search and browse after a migration from v1.5.3 to v2.0.1. It is possible for the Solr index to get messed up during an upgrade. Below is what Lyrasis recommended I do as a first step. It basically removes all old index data and forces an entire re-index. stop archivesspace back up /path/to/archivespace/data/ just in case (cp -a /path/to/archivespace/data/ /path/to/someplace/safe/) rm -rf /path/to/archivespace/data/* start archivesspace up again I suggest trying that and seeing if it helps. - Chelsea --------------- Chelsea Lobdell Library Web Developer/ Swarthmore College clobdel1 at swarthmore.edu / (610)690-6818 On Tue, Jul 18, 2017 at 9:55 AM, Kutzuba, Jamie > wrote: Hello- I upgraded our instance from 1.3.0 to 1.5.2 yesterday in order to move to 2.0. I can run archivesspace.bat and bring up the public and staff interfaces but the staff side is not showing any of the data. On the public side there is no browseable data. Searching on either interface will bring up the archival components (lower-down levels of a finding aid, like each file or item) but not the resource records themselves (collection-level records). If I click on an archival component it does bring me to its resource record, so the resources are still there, but they are not showing up in the searches nor in the browse section. Did the conversion go awry? Would it be best to roll back or is there something else I can do to resolve this? Running Windows Server 2012 R2, MySQL 5.6. Thanks for your help- Jamie Jamie Kutzuba Systems Librarian 315.781.4355 Warren Hunting Smith Library Hobart & William Smith Colleges _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From KUTZUBA at hws.edu Tue Jul 18 13:23:13 2017 From: KUTZUBA at hws.edu (Kutzuba, Jamie) Date: Tue, 18 Jul 2017 17:23:13 +0000 Subject: [Archivesspace_Users_Group] Upgrade from 1.3 to 1.5.2 - data issues References: <47bd0c0eac3942c8a2001f3787f04b5e@EXCH13MBX1.hws.edu> Message-ID: <30865d7904a44db2a855bf3b2438bb0b@EXCH13MBX1.hws.edu> Hello again- All I need to do to reindex is to run archivesspace.bat as admin and wait, right? Is there something in the log file that I can look for to know the process has been completed? It seems extremely slow. Is this the sort of thing I should be seeing in archivesspace.out? Jul 18, 2017 11:31:38 AM org.apache.solr.update.processor.LogUpdateProcessor finish INFO: [collection1] webapp= path=/update params={} {add=[/repositories/2/archival_objects/1, /repositories/2/archival_objects/2, /repositories/2/archival_objects/3, /repositories/2/archival_objects/4, /repositories/2/archival_objects/5, /repositories/2/archival_objects/6, /repositories/2/archival_objects/7, /repositories/2/archival_objects/8, /repositories/2/archival_objects/9, /repositories/2/archival_objects/10, ... (25 adds)]} 0 16 ~~~ Indexed 25 of 25307 archival_object records in repository 2 ( added 25 records in 3656.0ms ) ~~~ ~~~ Indexed 50 of 25307 archival_object records in repository 2 ( added 25 records in 3078.0ms ) ~~~ Jul 18, 2017 11:31:38 AM org.apache.solr.update.DirectUpdateHandler2 commit INFO: start commit{,optimize=false,openSearcher=false,waitSearcher=true,expungeDeletes=false,softCommit=false,prepareCommit=false} Jul 18, 2017 11:31:38 AM org.apache.solr.update.processor.LogUpdateProcessor finish INFO: [collection1] webapp= path=/update params={} {add=[/repositories/2/archival_objects/51, /repositories/2/archival_objects/52, /repositories/2/archival_objects/53, /repositories/2/archival_objects/54, /repositories/2/archival_objects/55, /repositories/2/archival_objects/56, /repositories/2/archival_objects/57, /repositories/2/archival_objects/58, /repositories/2/archival_objects/59, /repositories/2/archival_objects/60, ... (354 adds)]} 0 172 ~~~ Indexed 75 of 25307 archival_object records in repository 2 ( added 25 records in 3875.0ms ) ~~~ ~~~ Indexed 100 of 25307 archival_object records in repository 2 ( added 25 records in 3297.0ms ) ~~~ D, [2017-07-18T11:31:38.423000 #3620] DEBUG -- : Thread-1225772: GET /repositories/2/archival_objects?id_set=101%2C102%2C103%2C104%2C105%2C106%2C107%2C108%2C109%2C110%2C111%2C112%2C113%2C114%2C115%2C116%2C117%2C118%2C119%2C120%2C121%2C122%2C123%2C124%2C125&resolve%5B%5D=location_profile&resolve%5B%5D=container_profile&resolve%5B%5D=container_locations&resolve%5B%5D=subjects&resolve%5B%5D=linked_agents&resolve%5B%5D=linked_records&resolve%5B%5D=classifications&resolve%5B%5D=digital_object [session: #"search_indexer", :login_time=>2017-07-18 11:31:34 -0400, :expirable=>false}, @id="9ff1672a8591fd3b1fd746230b4c0bba11a7048a2418875ab8c4d80491918a79">] D, [2017-07-18T11:31:38.423000 #3620] DEBUG -- : Thread-351220: GET /repositories/2/archival_objects?id_set=126%2C127%2C128%2C129%2C130%2C131%2C132%2C133%2C134%2C135%2C136%2C137%2C138%2C139%2C140%2C141%2C142%2C143%2C144%2C145%2C146%2C147%2C148%2C149%2C150&resolve%5B%5D=location_profile&resolve%5B%5D=container_profile&resolve%5B%5D=container_locations&resolve%5B%5D=subjects&resolve%5B%5D=linked_agents&resolve%5B%5D=linked_records&resolve%5B%5D=classifications&resolve%5B%5D=digital_object [session: #"search_indexer", :login_time=>2017-07-18 11:31:34 -0400, :expirable=>false}, @id="9ff1672a8591fd3b1fd746230b4c0bba11a7048a2418875ab8c4d80491918a79">] D, [2017-07-18T11:31:38.439000 #3620] DEBUG -- : Thread-1225772: Post-processed params: {"id_set"=>[101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120, 121, 122, 123, 124, 125], "resolve"=>["location_profile", "container_profile", "container_locations", "subjects", "linked_agents", "linked_records", "classifications", "digital_object"], :repo_id=>2, "modified_since"=>0} D, [2017-07-18T11:31:38.439000 #3620] DEBUG -- : Thread-351220: Post-processed params: {"id_set"=>[126, 127, 128, 129, 130, 131, 132, 133, 134, 135, 136, 137, 138, 139, 140, 141, 142, 143, 144, 145, 146, 147, 148, 149, 150], "resolve"=>["location_profile", "container_profile", "container_locations", "subjects", "linked_agents", "linked_records", "classifications", "digital_object"], :repo_id=>2, "modified_since"=>0} D, [2017-07-18T11:31:38.439000 #3620] DEBUG -- : Thread-781488: GET /repositories/2/archival_objects?id_set=176%2C177%2C178%2C179%2C180%2C181%2C182%2C183%2C184%2C185%2C186%2C187%2C188%2C189%2C190%2C191%2C192%2C193%2C194%2C195%2C196%2C197%2C198%2C199%2C200&resolve%5B%5D=location_profile&resolve%5B%5D=container_profile&resolve%5B%5D=container_locations&resolve%5B%5D=subjects&resolve%5B%5D=linked_agents&resolve%5B%5D=linked_records&resolve%5B%5D=classifications&resolve%5B%5D=digital_object [session: #"search_indexer", :login_time=>2017-07-18 11:31:34 -0400, :expirable=>false}, @id="9ff1672a8591fd3b1fd746230b4c0bba11a7048a2418875ab8c4d80491918a79">] D, [2017-07-18T11:31:38.455000 #3620] DEBUG -- : Thread-781488: Post-processed params: {"id_set"=>[176, 177, 178, 179, 180, 181, 182, 183, 184, 185, 186, 187, 188, 189, 190, 191, 192, 193, 194, 195, 196, 197, 198, 199, 200], "resolve"=>["location_profile", "container_profile", "container_locations", "subjects", "linked_agents", "linked_records", "classifications", "digital_object"], :repo_id=>2, "modified_since"=>0} D, [2017-07-18T11:31:39.158000 #3620] DEBUG -- : Thread-1152130: Responded with [200, {"Content-Type"=>"application/json", "Cache-Control"=>"private, must-revalidate, max-age=0", "Content-Length"=>"3"}, ["[]\n"]]... in 60204.0ms D, [2017-07-18T11:31:39.158000 #3620] DEBUG -- : Thread-1102634: GET /repositories/2/archival_objects?id_set=151%2C152%2C153%2C154%2C155%2C156%2C157%2C158%2C159%2C160%2C161%2C162%2C163%2C164%2C165%2C166%2C167%2C168%2C169%2C170%2C171%2C172%2C173%2C174%2C175&resolve%5B%5D=location_profile&resolve%5B%5D=container_profile&resolve%5B%5D=container_locations&resolve%5B%5D=subjects&resolve%5B%5D=linked_agents&resolve%5B%5D=linked_records&resolve%5B%5D=classifications&resolve%5B%5D=digital_object [session: #"search_indexer", :login_time=>2017-07-18 11:31:34 -0400, :expirable=>false}, @id="9ff1672a8591fd3b1fd746230b4c0bba11a7048a2418875ab8c4d80491918a79">] D, [2017-07-18T11:31:39.158000 #3620] DEBUG -- : Thread-1102634: Post-processed params: {"id_set"=>[151, 152, 153, 154, 155, 156, 157, 158, 159, 160, 161, 162, 163, 164, 165, 166, 167, 168, 169, 170, 171, 172, 173, 174, 175], "resolve"=>["location_profile", "container_profile", "container_locations", "subjects", "linked_agents", "linked_records", "classifications", "digital_object"], :repo_id=>2, "modified_since"=>0} D, [2017-07-18T11:31:39.455000 #3620] DEBUG -- : Thread-1225772: Responded with [200, {"Content-Type"=>"application/json", "Cache-Control"=>"private, must-revalidate, max-age=0", "Content-Length"=>"66020"}, ["[{\"lock_version\":0,\"position\":100,\"publish\":true,\"ref_id\":\"ref198_n2v\",\"title\":\"Bk. 8, #33 The Catholic Church of Geneva, NY\",\"display_string\":\"Bk. 8, #33 The Catholic Church of Geneva, NY\",\"restrictions_apply\":false,\"created_by\":\"admin\",\"last_modified_by\":\"admin\",\"create_time\":\"2014-09-19T13:20:21Z\",\"system_mtime\":\"2017-07-17T18:12:28Z\",\"user_m... in 1047.0ms D, [2017-07-18T11:31:39.533000 #3620] DEBUG -- : Thread-351220: Responded with [200, {"Content-Type"=>"application/json", "Cache-Control"=>"private, must-revalidate, max-age=0", "Content-Length"=>"64653"}, ["[{\"lock_version\":0,\"position\":125,\"publish\":true,\"ref_id\":\"ref228_10q\",\"title\":\"Bk. 12, #59 Geneva Academy and Geneva College [Chronological Table]\",\"display_string\":\"Bk. 12, #59 Geneva Academy and Geneva College [Chronological Table]\",\"restrictions_apply\":false,\"created_by\":\"admin\",\"last_modified_by\":\"admin\",\"create_time\":\"2014-09-19T13:20:21Z\",\"sy... in 1125.0ms D, [2017-07-18T11:31:39.611000 #3620] DEBUG -- : Thread-781488: Responded with [200, {"Content-Type"=>"application/json", "Cache-Control"=>"private, must-revalidate, max-age=0", "Content-Length"=>"71425"}, ["[{\"lock_version\":0,\"position\":175,\"publish\":true,\"ref_id\":\"ref287_9b8\",\"title\":\"Bk. 15, #108 Y.M.C.A. Tug of War\",\"display_string\":\"Bk. 15, #108 Y.M.C.A. Tug of War\",\"restrictions_apply\":false,\"created_by\":\"admin\",\"last_modified_by\":\"admin\",\"create_time\":\"2014-09-19T13:20:22Z\",\"system_mtime\":\"2017-07-17T18:12:28Z\",\"user_mtime\":\"2014-09-19T13:2... in 1188.0ms D, [2017-07-18T11:31:39.673000 #3620] DEBUG -- : Thread-1102634: Responded with [200, {"Content-Type"=>"application/json", "Cache-Control"=>"private, must-revalidate, max-age=0", "Content-Length"=>"68756"}, ["[{\"lock_version\":0,\"position\":150,\"publish\":true,\"ref_id\":\"ref255_lho\",\"title\":\"Bk. 14, #83 Letters to Former Hobart College President\",\"display_string\":\"Bk. 14, #83 Letters to Former Hobart College President, 1936\",\"restrictions_apply\":false,\"created_by\":\"admin\",\"last_modified_by\":\"admin\",\"create_time\":\"2014-09-19T13:20:22Z\",\"system_mtime\":\"2017-... in 1250.0ms D, [2017-07-18T11:31:39.939000 #3620] DEBUG -- : Thread-1252000: Responded with [200, {"Content-Type"=>"application/json", "Cache-Control"=>"private, must-revalidate, max-age=0", "Content-Length"=>"3"}, ["[]\n"]]... in 60969.0ms Jul 18, 2017 11:31:40 AM org.apache.solr.update.processor.LogUpdateProcessor finish INFO: [collection1] webapp= path=/update params={} {add=[/repositories/2/archival_objects/126, /repositories/2/archival_objects/127, /repositories/2/archival_objects/128, /repositories/2/archival_objects/129, /repositories/2/archival_objects/130, /repositories/2/archival_objects/131, /repositories/2/archival_objects/132, /repositories/2/archival_objects/133, /repositories/2/archival_objects/134, /repositories/2/archival_objects/135, ... (25 adds)]} 0 0 Jul 18, 2017 11:31:40 AM org.apache.solr.update.processor.LogUpdateProcessor finish INFO: [collection1] webapp= path=/update params={} {add=[/repositories/2/archival_objects/151, /repositories/2/archival_objects/152, /repositories/2/archival_objects/153, /repositories/2/archival_objects/154, /repositories/2/archival_objects/155, /repositories/2/archival_objects/156, /repositories/2/archival_objects/157, /repositories/2/archival_objects/158, /repositories/2/archival_objects/159, /repositories/2/archival_objects/160, ... (25 adds)]} 0 0 Jul 18, 2017 11:31:40 AM org.apache.solr.update.processor.LogUpdateProcessor finish INFO: [collection1] webapp= path=/update params={} {add=[/repositories/2/archival_objects/101, /repositories/2/archival_objects/102, /repositories/2/archival_objects/103, /repositories/2/archival_objects/104, /repositories/2/archival_objects/105, /repositories/2/archival_objects/106, /repositories/2/archival_objects/107, /repositories/2/archival_objects/108, /repositories/2/archival_objects/109, /repositories/2/archival_objects/110, ... (25 adds)]} 0 0 ~~~ Indexed 125 of 25307 archival_object records in repository 2 ( added 25 records in 2234.0ms ) ~~~ ~~~ Indexed 150 of 25307 archival_object records in repository 2 ( added 25 records in 2172.0ms ) ~~~ ~~~ Indexed 175 of 25307 archival_object records in repository 2 ( added 25 records in 2203.0ms ) ~~~ D, [2017-07-18T11:31:40.658000 #3620] DEBUG -- : Thread-351220: POST /update_monitor [session: #"staff_system", :login_time=>2017-07-18 10:52:15 -0400, :expirable=>false}, @id="5df814ae339a635a5eb39bb8a9ea1767ba5c66c881f67db19056d09c1d981139">] D, [2017-07-18T11:31:40.658000 #3620] DEBUG -- : Thread-351220: Post-processed params: {:active_edits=>#"active_edits", "active_edits"=>[]}>} D, [2017-07-18T11:31:40.673000 #3620] DEBUG -- : Thread-351220: Responded with [200, {"Content-Type"=>"application/json", "Cache-Control"=>"private, must-revalidate, max-age=0", "Content-Length"=>"3"}, ["{}\n"]]... in 734.0ms Jul 18, 2017 11:31:40 AM org.apache.solr.update.processor.LogUpdateProcessor finish AND also Jul 18, 2017 12:55:10 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: Rendered search/_components_switch.html.erb (0.0ms) Jul 18, 2017 12:55:10 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: Rendered search/_filter.html.erb (0.0ms) Jul 18, 2017 12:55:10 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: Rendered search/_inline_results.html.erb (0.0ms) Jul 18, 2017 12:55:10 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: Rendered search/results.html.erb within layouts/application (0.0ms) Jul 18, 2017 12:55:10 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: Rendered C:/archivesspace-v1.5.2/archivesspace/plugins/local/public/views/site/_branding.html.erb (0.0ms) Jul 18, 2017 12:55:10 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: Rendered C:/archivesspace-v1.5.2/archivesspace/plugins/local/public/views/site/_header.html.erb (0.0ms) Jul 18, 2017 12:55:10 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: Rendered site/_advanced_search.html.erb (16.0ms) Jul 18, 2017 12:55:10 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: Rendered site/_breadcrumb.html.erb (0.0ms) Jul 18, 2017 12:55:10 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: Rendered C:/archivesspace-v1.5.2/archivesspace/plugins/local/public/views/site/_footer.html.erb (0.0ms) Jul 18, 2017 12:55:10 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: Completed 200 OK in 1141.0ms (Views: 31.0ms) Thanks- Jamie 315.781.4355 From: Kutzuba, Jamie Sent: Tuesday, July 18, 2017 11:04 AM To: Archivesspace Users Group Subject: RE: [Archivesspace_Users_Group] Upgrade from 1.3 to 1.5.2 - data issues Hi Chelsea- Thanks. I?m giving that a go now. - Jamie 315.781.4355 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chelsea Lobdell Sent: Tuesday, July 18, 2017 10:25 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Upgrade from 1.3 to 1.5.2 - data issues Hi Jamie, TriCo Libraries recently experienced issues with search and browse after a migration from v1.5.3 to v2.0.1. It is possible for the Solr index to get messed up during an upgrade. Below is what Lyrasis recommended I do as a first step. It basically removes all old index data and forces an entire re-index. stop archivesspace back up /path/to/archivespace/data/ just in case (cp -a /path/to/archivespace/data/ /path/to/someplace/safe/) rm -rf /path/to/archivespace/data/* start archivesspace up again I suggest trying that and seeing if it helps. - Chelsea --------------- Chelsea Lobdell Library Web Developer/ Swarthmore College clobdel1 at swarthmore.edu / (610)690-6818 On Tue, Jul 18, 2017 at 9:55 AM, Kutzuba, Jamie > wrote: Hello- I upgraded our instance from 1.3.0 to 1.5.2 yesterday in order to move to 2.0. I can run archivesspace.bat and bring up the public and staff interfaces but the staff side is not showing any of the data. On the public side there is no browseable data. Searching on either interface will bring up the archival components (lower-down levels of a finding aid, like each file or item) but not the resource records themselves (collection-level records). If I click on an archival component it does bring me to its resource record, so the resources are still there, but they are not showing up in the searches nor in the browse section. Did the conversion go awry? Would it be best to roll back or is there something else I can do to resolve this? Running Windows Server 2012 R2, MySQL 5.6. Thanks for your help- Jamie Jamie Kutzuba Systems Librarian 315.781.4355 Warren Hunting Smith Library Hobart & William Smith Colleges _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From pat_frade at byu.edu Tue Jul 18 15:36:33 2017 From: pat_frade at byu.edu (Pat Frade) Date: Tue, 18 Jul 2017 19:36:33 +0000 Subject: [Archivesspace_Users_Group] Migration from 1.4.2 to 1.5.4 Message-ID: <22ca0500fc3e4a94ad0dfb02f60b7521@MB7.byu.local> Over the last year we have made multiple attempts to migrate from 1.4 to 1.5. Recently we had a successful migration to our dev server with no errors with our data. However, we attempted to migrate to our staging server using that same data and received the same errors as previous attempts. We have received three types of errors with different messages. Examples are listed below and what action was taken to fix said error. All of our actions were conducted in our production server and not our dev server. Error Message Action AspaceJsonToManagedContainerMapper: :LocationMismatchException container_locations -- Locations in ArchivesSpace container don't match locations in existing top container Verified that locations for each top container matched JSONModel::ValidationException barcode_1 -- Mismatch when mapping between barcode and barcode_1 Verified that barcodes matched each top container, no white spaces were used, and barcodes were not used for other boxes JSONModel::ValidationException indicator_1 -- Mismatch when mapping between indicator and indicator_1 Verified that the above were correct and then replaced the instance Does anybody have any suggestions as to what could be the issue? Would having different information in the instances required fields (type, location status, and location start date) cause an issue? Thank you for your assistance. Matthew Leavitt Collection Management Archivist 1191 Harold B. Lee Library Brigham Young University Provo, UT 84602 801-422-1179 Matthew_leavitt at byu.edu Pat Frade Manuscript Cataloger 6741 Harold B. Lee Library Brigham Young University Provo, UT 84602 801-422-6730 pat_frade at byu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From seth.shaw at unlv.edu Tue Jul 18 16:55:47 2017 From: seth.shaw at unlv.edu (Seth Shaw) Date: Tue, 18 Jul 2017 13:55:47 -0700 Subject: [Archivesspace_Users_Group] Plugin causing RDE validation error Message-ID: *Apologies for cross-listing, trying to figure out where best to post this type of question.* I just inherited a plugin that adds a "publish" boolean value to an extent note to allow recording both linear and cubic feet but only publish one of them (https://github.com/UNLV-Libraries/ArchivesSpace-authority-project/tree/master/extents_ext). It appears to work fine, however it causes a validation error on the rapid data entry right away (before any data entry begins). I'm not sure why the validator is complaining; other elements that have required components (e.g. you can't just enter and end date) but it doesn't complain until there is data entered whereas it now complains about extent automatically. I've included request and response data from a test below; the same form data can be sent when the plugin is and isn't enabled. Without the plugin it simply reports the level of description being absent (expected). With the plugin enabled it also reports extent values missing (which shouldn't happen unless we have entered data first). You can see from the plugin source that we've simply added a simple schema extension. Any idea why this is causing the validator to complain and, more importantly, how to resolve it? Thanks. For reference: Validation Call Request Headers: POST /archival_objects/validate_rows HTTP/1.1 Host: archivestest:8080 Connection: keep-alive Content-Length: 3065 Origin: http://archivestest:8080 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36 Content-Type: application/x-www-form-urlencoded; charset=UTF-8 Accept: application/json, text/javascript, */*; q=0.01 X-Requested-With: XMLHttpRequest Referer: http://archivestest:8080/resources/1039/edit Accept-Encoding: gzip, deflate Accept-Language: en-US,en;q=0.8 **Cookie and CSFR Tokens Removed** Form Data (prettified): archival_record_children[children][0][level]: archival_record_children[children][0][other_level]: archival_record_children[children][0][publish]: 1 archival_record_children[children][0][title]: archival_record_children[children][0][component_id]: archival_record_children[children][0][language]: archival_record_children[children][0][dates][0][expression]: archival_record_children[children][0][dates][0][date_type]: archival_record_children[children][0][dates][0][label]: archival_record_children[children][0][dates][0][begin]: archival_record_children[children][0][dates][0][end]: archival_record_children[children][0][extents][0][portion]: archival_record_children[children][0][extents][0][number]: archival_record_children[children][0][extents][0][extent_type]: archival_record_children[children][0][extents][0][container_summary]: archival_record_children[children][0][extents][0][physical_details]: archival_record_children[children][0][extents][0][dimensions]: archival_record_children[children][0][instances][0][instance_type]: archival_record_children[children][0][instances][0][container][type_1]: archival_record_children[children][0][instances][0][container][indicator_1]: archival_record_children[children][0][instances][0][container][barcode_1]: archival_record_children[children][0][instances][0][container][type_2]: archival_record_children[children][0][instances][0][container][indicator_2]: archival_record_children[children][0][instances][0][container][type_3]: archival_record_children[children][0][instances][0][container][indicator_3]: archival_record_children[children][0][notes][0][type]: archival_record_children[children][0][notes][0][jsonmodel_type]: note_singlepart archival_record_children[children][0][notes][0][label]: archival_record_children[children][0][notes][0][content][0]: archival_record_children[children][0][notes][1][type]: archival_record_children[children][0][notes][1][jsonmodel_type]: note_singlepart archival_record_children[children][0][notes][1][label]: archival_record_children[children][0][notes][1][content][0]: archival_record_children[children][0][notes][2][type]: archival_record_children[children][0][notes][2][jsonmodel_type]: note_singlepart archival_record_children[children][0][notes][2][label]: archival_record_children[children][0][notes][2][content][0]: (empty) validate_only: true Response without the plugin: [{"errors":{"level":["Property is required but was missing"]}}] Response withe the plugin: [{"errors":{"extents/0/portion":["Property is required but was missing"],"extents/0/number":["Property is required but was missing"],"extents/0/extent_type":["Property is required but was missing"],"level":["Property is required but was missing"]}}] From christine.dibella at lyrasis.org Wed Jul 19 09:50:03 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Wed, 19 Jul 2017 13:50:03 +0000 Subject: [Archivesspace_Users_Group] information for those not attending the ArchivesSpace Member Forum Message-ID: We're looking forward to seeing so many of you at the ArchivesSpace Member Forum in Portland on July 25. More information on the program is online at https://archivesspace.atlassian.net/wiki/display/ADC/ArchivesSpace+Member+Forum+2017 and we are still accepting online registrations for this free event. If you can't attend the Forum, or can only come to part, here's some information on Forum-related activities in which you may want to partake. All are welcome to participate in any of the options below, so feel free to forward this information to others interested in ArchivesSpace. Post-Forum Mixer There will be a post-Forum mixer, co-hosted by our Registered Service Providers Atlas Systems and LYRASIS, at the Hilton Portland in the Skyline Room from 5:30-7:00 p.m. Extend your conversations from the Member Forum, or, if you weren't able to join us for the Forum, come for some light food and drink and to catch up with other ArchivesSpace users as a warmup to your evening in Portland. If you're not registered for the Forum, an RSVP to christine.dibella at lyrasis.org is appreciated. Big thanks especially to Dan Specht at Atlas and John Herbert at LYRASIS for making this possible! Livestream The morning presentations (9:00-11:30 a.m. PDT) and the concluding lightning round and wrap up (4:00-5:30 p.m. PDT) will be livestreamed at http://www.ustream.tv/channel/psu-live-a (the livestream will be available at the time of the event). You will be able to ask questions using the chat feature of UStream and planning group members will be monitoring the chat to ask questions of presenters as needed. Recordings, Notes, and Presentations Selected sessions will be recorded. The recordings, along with presentations and community-sourced notes, will be posted to the Member Forum wiki page soon after the event. Twitter Whether you're at the Forum or not, if you're on Twitter, we encourage you to tweet any portion of the meeting - or to tweet questions for the meeting sessions from afar - using our suggested hashtag: #aspace17 Questions If you have any questions about the Forum itself or these options, please don't hesitate to get in touch. We look forward to connecting with many of you, in person or virtually, next week. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 13904 bytes Desc: image001.jpg URL: From christine.dibella at lyrasis.org Wed Jul 19 14:07:58 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Wed, 19 Jul 2017 18:07:58 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace v2.1.0 released Message-ID: The ArchivesSpace team is pleased to release version 2.1.0! ArchivesSpace 2.1.0 features very substantial work from Hudson Molonglo (HM) as well as code contributions from community members. This release includes the production-ready new Public User Interface, as well as a beginning OAI-PMH responder, an expanded rights management module, and other smaller items. You can download the new release from Github at https://github.com/archivesspace/archivesspace/releases/tag/v2.1.0. Please see the technical documentation for information on how to upgrade your ArchivesSpace installations. Please note that because the old container code was removed for this release, there are some additional considerations if you are using a version of ArchivesSpace older than 1.5.0. Also, if you currently use rights statements, your data will be migrated to the new data model as part of the upgrade process. This was a true community effort, and thanks to all who contributed, wrote specifications, participated in testing the release candidates, and provided the feedback that led to the many improvements in this release. Particular thanks to * Mark Custer for his tireless leadership of the Public User Interface Enhancement Project * Susan Pyzynski, Cory Nimer, and Scott Schwartz for their intrepid testing of the PUI in its development phase * The many members who participated over the course of the PUI effort, including Bobbi Fox, Melissa Wisner, Maura Carbone, Krista Ferrante, Linda Hocking, Sue Luftschein, Matt Francis, Claryn Spies, Mariella Soprano, Elisa Piccio, Dara Flynn, Jessica Dowd Crouch, and Cate Putrirskis. * Yale University and Harvard University for their financial and development support of the PUI effort * Max Eckard, Brad Westbrook, and Hillel Arnold for writing the rights statements specification * Cory Nimer, Gordon Daines, and Jason Loeffler for writing the OAI-PMH specification, and Carolyn Runyon for her substantial comments that improved it Community pull requests from Steve Majewski, Dave Mayo, Br. Paul (@Perticus), Chris Fitzpatrick, Clay Oster, and Mohamed Mohideen Abdul Rasheed also improved this release. Thanks as always to Mark Cooper and Blake Carver of LYRASIS DTS for their technical support. We are very happy to bring this long-awaited release to you and welcome your feedback. Please let us know if you have questions or encounter problems executing the upgrade. We expect to put out a minor ArchivesSpace release in mid-August. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 13904 bytes Desc: image003.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.jpg Type: image/jpeg Size: 5872 bytes Desc: image004.jpg URL: From christine.dibella at lyrasis.org Thu Jul 20 13:05:09 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Thu, 20 Jul 2017 17:05:09 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Update - July 2017 Message-ID: [ASpaceOrgHome.jpg] July 2017 Update ArchivesSpace 2.1.0 Now Available The ArchivesSpace team is pleased to release version 2.1.0! ArchivesSpace 2.1.0 features very substantial work from Hudson Molonglo (HM) as well as code contributions from community members. This release includes the production-ready new Public User Interface, as well as a beginning OAI-PMH responder, an expanded rights management module, and other smaller items. You can download the new release from Github at https://github.com/archivesspace/archivesspace/releases/tag/v2.1.0. Please see the technical documentation for information on how to upgrade your ArchivesSpace installations. Please note that because the old container code was removed for this release, there are some additional considerations if you are using a version of ArchivesSpace older than 1.5.0. Also, if you currently use rights statements, your data will be migrated to the new data model as part of the upgrade process. This was a true community effort, and thanks to all who contributed, wrote specifications, participated in testing the release candidates, and provided the feedback that led to the many improvements in this release. Particular thanks to * Mark Custer for his tireless leadership of the Public User Interface Enhancement Project * Susan Pyzynski, Cory Nimer, and Scott Schwartz for their intrepid testing of the PUI in its development phase * The many members who participated over the course of the PUI effort, including Bobbi Fox, Melissa Wisner, Maura Carbone, Krista Ferrante, Linda Hocking, Sue Luftschein, Matt Francis, Claryn Spies, Mariella Soprano, Elisa Piccio, Dara Flynn, Jessica Dowd Crouch, and Cate Putrirskis. * Yale University and Harvard University for their financial and development support of the PUI effort * Max Eckard, Brad Westbrook, and Hillel Arnold for writing the rights statements specification * Cory Nimer, Gordon Daines, and Jason Loeffler for writing the OAI-PMH specification, and Carolyn Runyon for her substantial comments that improved it Community pull requests from Steve Majewski, Dave Mayo, Br. Paul (@Perticus), Chris Fitzpatrick, Clay Oster, and Mohamed Mohideen Abdul Rasheed also improved this release. Thanks as always to Mark Cooper and Blake Carver of LYRASIS DTS for their technical support. We are very happy to bring this long-awaited release to you and welcome your feedback. Please let us know if you have questions or encounter problems executing the upgrade. We expect to put out a minor ArchivesSpace release in mid-August. Staffing News LYRASIS, the organizational home for ArchivesSpace, is pleased to announce that Christine "Kim" Kim has joined us as our Community Engagement Coordinator. Kim worked in a variety of roles in Special Collections & Archives at ArchivesSpace charter member institution University of California Irvine (UCI) since 2010. With ArchivesSpace, she was first involved in helping to ensure UCI's smooth transition from Archivists' Toolkit, and used the ArchivesSpace application and supervises others in their use of it on a daily basis. Her ArchivesSpace-specific activities at UCI included testing migrations and features, developing and implementing workflows, creating user documentation, training, and working closely with staff, students, and IT support to make the application work for all. Her most recent position at UCI combined technical services, public services, and outreach activities, giving her a broad view of archives and the needs of different kinds of users of archives. She took a lead role in developing dynamic campus and community programming to highlight materials in Special Collections & Archives, including a now annual ZineFest that promotes UCI's rich collections of handmade, community-centric zines and gives participants chances to engage with and produce their own content. She received her MLIS from San Jose State University and has an undergraduate degree from UCI with a dual major in Film & Media Studies and History. As Community Engagement Coordinator, Kim will be responsible for user support, training, outreach, and communications across the ArchivesSpace community and will work especially closely with the User Documentation and Testing sub-teams of our Advisory Councils. One of her first priorities will be working with Christine Di Bella and the rest of the ArchivesSpace team to develop engaging programming and other opportunities for ArchivesSpace users to share their expertise with each other in person and online. LYRASIS serves as the organizational home for ArchivesSpace, providing resources and services to help grow, support and amplify the community contributions. These include staff, technology, financial services and logistics support. The ArchivesSpace team, consisting of Christine Di Bella, Program Manager, Laney McGlohon, Technical Lead, and now Christine Kim, Community Engagement Coordinator, reports to Laurie Arp, LYRASIS's Director of Collections Services & Community Supported Software. Kim's first day was July 10 and we're especially pleased that she'll be part of our Member Forum and other activities in conjunction with SAA in Portland. She will continue to be based in Southern California, but is sure to become a lively presence on our listservs and a familiar face as she represents ArchivesSpace at conferences and in other venues. Request for Comments: Agents Module Expansion Specification On behalf of the Specification Team: Sue Luftschein, Cory Nimer, and Bradley Westbrook In an effort begun over two years ago, an ad-hoc team from the Technical Advisory Committee has been working to develop specifications to expand the ArchivesSpace Agent module to more fully support EAC-CPF and the MARC Authority format, and to assist with integration with the Social Networks and Archival Context (SNAC) Cooperative. This group has included representatives from the ArchivesSpace program team, Brigham Young University, and the University of Southern California. The current draft of the specification is now available for comment and includes these components: * Data Model: https://docs.google.com/spreadsheets/d/1HFBCQ6hnsr92gaSqs2cWSkRRtwySstHQv_B74XnYxKw/edit?usp=sharing * Software Requirements Specification: https://docs.google.com/document/d/1aFz4hzFWYVFo8TLkUpZS97cr1QfRgO4-st_G7wU8z2I/edit?usp=sharing * Wireframes: https://drive.google.com/drive/folders/0B1AAa_XOzd58OGFxVWdzNDM3d0k?usp=sharing * Migration Maps: https://drive.google.com/drive/folders/0B1AAa_XOzd58a3dVNkpYdXVTWlk?usp=sharing These are also linked from the overall JIRA issue for Agents enhancements at https://archivesspace.atlassian.net/browse/AR-1779. The current version of the specification aims to provide augmented functionality in the following areas: * Record input Introduces a range of new elements for the description of archival creators and authority record management. This includes a revised model for dates based on the EAC-CPF standard. * Record ingest Includes expanded functionality for the implementation of EAC-CPF and MARC. Documentation of updated mappings for these ingest routines is provided. * Record merging Expands on existing merging functionality, allowing for element-by-element selection from individual records during merge. * Record export Introduces revised export routines to provide greater compatibility with EAC-CPF and MARC. Documentation of updated mappings is provided. * Record transmission Provides for submission of locally-created Agent records to the SNAC Cooperative using a JSON response. * Record synchronization Introduces functionality to allow institutions to maintain synchronization of local Agent record content with the Library of Congress Name Authority File (LCNAF) and SNAC. The specification team requests feedback from institutions and individual archivists. Member comments can be posted directly to the individual specification documents or emailed to ArchivesSpaceHome at lyrasis.org. Cory, Brad, and Sue will also be presenting information on the specification and leading a focus group at the Member Forum on July 25. EAD3 Export for ArchivesSpace Being Developed Through Partnership of NC State and Duke We're pleased to announce that community members Trevor Thornton of North Carolina State University and Noah Huffman of Duke University are taking the lead this summer on building an exporter that will provide a first level of EAD3 support in the ArchivesSpace application. Trevor will be doing the development and Noah will be providing leadership and guidance from the functional side of things. Their work will be based on the mapping for EAD3 that the Migrations sub-team of our Technical Advisory Council circulated in the community earlier this year. The initial focus is on ArchivesSpace being able to export valid EAD3. Building on this work, the program will continue to consider how to provide additional levels of support - with help in this area always much appreciated. As work proceeds, you will be able to comment on and track progress in the JIRA issue: https://archivesspace.atlassian.net/browse/AR-923 as well as in Trevor's Github development fork for the project: https://github.com/NCSU-Libraries/archivesspace/tree/ead3_export. For questions about the EAD3 exporter project, please contact Noah (noah.huffman at duke.edu) or Trevor (trthorn2 at ncsu.edu). For questions or ideas about EAD3 support overall, feel free to post to the JIRA issue or get in touch with Christine (christine.dibella at lyrasis.org). Thanks to Trevor and Noah and their institutions for their generosity in taking on this project. If you or your institution are interested in getting more involved in development for ArchivesSpace, and either have projects in mind or want to know about projects already prioritized by the community, please get in touch with Christine or Laney McGlohon (laney.mcglohon at lyrasis.org). Harvard Shares Plugin to Support Bulk Uploading of Archival Objects via Excel Spreadsheet (If you have a great plugin to share, please get in touch - we'd love to include it in a monthly update!) >From Bobbi Fox, Maintainer Library Technology Services, which supports the Harvard Library, is pleased to announce the availability of a new plugin, aspace-import-excel, available on GitHub at https://github.com/harvard-library/aspace-import-excel . Using the provided spreadsheet template, users can go to a Resource, and either add or insert the set of Archival Objects that have been defined in the spreadsheet. Please note carefully the following paragraph in the README: The intention is not to completely reproduce a Finding Aid as presented in an EAD XML, or to allow for every permutation of Archival Object creation within ArchivesSpace. We are aiming for the "80% rule"; that is, at least 80% of the work that would be done interactively can be replaced by an excel spreadsheet; additional refinements to individual archival objects (such as addition of agents-as-subjects, assignment of locations to top-level containers, etc.) would take place interactively. Installation information is on the main README file, with User Documentation at https://github.com/harvard-library/aspace-import-excel/blob/master/user_documentation/USER_DOCUMENTATION.md , including workflow, step by step usage, and extensive (exhaustive? :-) explanation of the Spreadsheet Template. This plugin was designed to aid the Harvard Library archival community, but we hope that it may be useful to other archivists in the ArchivesSpace community. Pull requests welcome. If you encounter problems, please create an issue on the GitHub repository. ArchivesSpace Member Forum We're looking forward to our third annual ArchivesSpace Member Forum in Portland on July 25. More information on the program is online at https://archivesspace.atlassian.net/wiki/display/ADC/ArchivesSpace+Member+Forum+2017 and we are still accepting online registrations for this free event open to any staff member of an ArchivesSpace member institution. If you can't attend the Forum, or can only come to part, here's some information on Forum-related activities in which you may want to partake. All are welcome to participate in any of the options below. Post-Forum Mixer There will be a post-Forum mixer, co-hosted by our Registered Service Providers Atlas Systems and LYRASIS, at the Hilton Portland in the Skyline Room from 5:30-7:00 p.m. Extend your conversations from the Member Forum, or, if you weren't able to join us for the Forum, come for some light food and drink and to catch up with other ArchivesSpace users as a warmup to your evening in Portland. If you're not registered for the Forum, an RSVP to christine.dibella at lyrasis.org is appreciated. Big thanks especially to Dan Specht at Atlas and John Herbert at LYRASIS for making this possible! Livestream The morning presentations (9:00-11:30 a.m. PDT) and the concluding lightning round and wrap up (4:00-5:30 p.m. PDT) will be livestreamed at http://www.ustream.tv/channel/psu-live-a (the livestream will be available at the time of the event). You will be able to ask questions using the chat feature of UStream and planning group members will be monitoring the chat to ask questions of presenters as needed. Recordings, Notes, and Presentations Selected sessions will be recorded. The recordings, along with presentations and community-sourced notes, will be posted to the Member Forum wiki page during or soon after the event. Twitter Whether you're at the Forum or not, if you're on Twitter, we encourage you to tweet any portion of the meeting - or to tweet questions for the meeting sessions from afar - using our suggested hashtag: #aspace17 Membership Update Our new members since June 6 include: * Iliff School of Theology (Colorado) * Moraine Valley Community College (Illinois) * Seattle Public School District #1 Archives * Southeastern Baptist Theological Seminary (North Carolina) * University of Northern Iowa * University of Oxford As of July 20, we have 330 General members, 14 Educational Program members, and 3 Registered Service Providers. If you are interested in your institution becoming a member of ArchivesSpace, please email us at ArchivesSpaceHome at lyrasis.org for more information. ArchivesSpace at SAA We're gearing up for the Society of American Archivists (SAA) annual meeting in Portland next week and look forward to seeing many of you there. Here's where you can find the ArchivesSpace during SAA: ArchivesSpace events or featuring ArchivesSpace staff * ArchivesSpace Member Forum, Smith Memorial Student Union, Portland State University, July 25 (registration required) * Post-Forum Mixer (co-hosted by Registered Service Providers Atlas Systems and LYRASIS), Hilton Portland, August 2, 5:30-7:00 p.m. Extend your conversations from the Member Forum, or, if you weren't able to join us for the Forum, come for light food and drink and to catch up with other ArchivesSpace users as a warmup to your evening in Portland. An RSVP to christine.dibella at lyrasis.org from those not registered for the Forum would be appreciated so that we are sure to have enough on hand. * Exhibit Hall, July 27-28 (opens July 27 at 5:00 p.m. and closes on July 28 at 4:30 p.m.; staff from ArchivesSpace and LYRASIS will be present at all times the exhibit hall is open) * Collection Management Tools Section, July 26, 2:30-3:45 p.m. - short presentation by Christine Di Bella * S401: Building Better Bridges: Strategies and Best Practices for Engaging Archival Communities: Friday, July 28, 10:00-11:00 a.m. - Building Better Bridges: Strategies and Best Practices for Engaging Archival Communities - featuring Christine Di Bella Events with information about ArchivesSpace led by ArchivesSpace users * S305: Systems Integration and the Archival Enterprise, Friday, July 28, 8:30-9:45 a.m. - featuring ArchivesSpace members Max Eckard, Patrick Galligan, Bonnie Gordon, Jason Loeffler, Dallas Pillen * S403: User-Centered Collaboration for Archival Discovery, Friday, July 28, 10:00-11:00 a.m. - featuring Harvard's Susan Pyzynski and Emilie Hardman, and James Bullen from Hudson Molonglo talking about the process for designing and developing the new public interface for ArchivesSpace. * Graduate Student poster 5: Migration as Motivation: Upgrading Legacy Finding Aids in Preparation for ArchivesSpace, Robert Richardson and Bethany Scott, University of North Texas / University of Houston ArchivesSpace monthly updates provide news about ArchivesSpace community and program activities and are sent to our member listservs, the ArchivesSpace Google Group, and SAA's Collection Management Tools roundtable listserv, as well as being posted on the ArchivesSpace website. Please feel free to share this update with people you know who have an interest in ArchivesSpace but may not be on one of these lists. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 19961 bytes Desc: image002.jpg URL: From bthomas at tsl.texas.gov Thu Jul 27 09:41:51 2017 From: bthomas at tsl.texas.gov (Brian Thomas) Date: Thu, 27 Jul 2017 13:41:51 +0000 Subject: [Archivesspace_Users_Group] Accessions plug-in for auto-numbering Message-ID: Has anyone written a plug-in for auto-generation of the next available accession identifier? I know that there is one already existing for next resource (thanks DU staff), maybe someone has modified that to work with accessions instead? We use a two part accession identifier, so that might throw a wrench into the situation as well. Thanks, Brian Thomas Electronic Records Specialist Texas State Library and Archives Commission 1201 Brazos Street Austin, TX 78701 PH: (512) 475-3374 e-mail: bthomas at tsl.texas.gov tsl.texas.gov [cid:image001.jpg at 01D029A2.37194C70] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5314 bytes Desc: image001.png URL: From bthomas at tsl.texas.gov Thu Jul 27 09:43:46 2017 From: bthomas at tsl.texas.gov (Brian Thomas) Date: Thu, 27 Jul 2017 13:43:46 +0000 Subject: [Archivesspace_Users_Group] Accessions plug-in for auto-numbering Message-ID: Please disregard that last question. I found something (thanks again DU!) From: Brian Thomas Sent: Thursday, July 27, 2017 8:42 AM To: Archivesspace Users Group Subject: Accessions plug-in for auto-numbering Has anyone written a plug-in for auto-generation of the next available accession identifier? I know that there is one already existing for next resource (thanks DU staff), maybe someone has modified that to work with accessions instead? We use a two part accession identifier, so that might throw a wrench into the situation as well. Thanks, Brian Thomas Electronic Records Specialist Texas State Library and Archives Commission 1201 Brazos Street Austin, TX 78701 PH: (512) 475-3374 e-mail: bthomas at tsl.texas.gov tsl.texas.gov [cid:image001.jpg at 01D029A2.37194C70] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5314 bytes Desc: image001.png URL: From michael.rush at yale.edu Thu Jul 27 09:56:57 2017 From: michael.rush at yale.edu (Rush, Michael) Date: Thu, 27 Jul 2017 13:56:57 +0000 Subject: [Archivesspace_Users_Group] Accessions plug-in for auto-numbering In-Reply-To: References: Message-ID: Brian, Disregarding your disregard, in case you need another option, you could check out the plugin we use at Yale for that very purpose: https://github.com/hudmol/aspace_yale_accessions. Best, Mike __________________________________ Michael Rush Assistant Head of the Manuscript Unit Beinecke Rare Book and Manuscript Library Yale University 203-432-8123 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Brian Thomas Sent: Thursday, July 27, 2017 6:44 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Accessions plug-in for auto-numbering Please disregard that last question. I found something (thanks again DU!) From: Brian Thomas Sent: Thursday, July 27, 2017 8:42 AM To: Archivesspace Users Group Subject: Accessions plug-in for auto-numbering Has anyone written a plug-in for auto-generation of the next available accession identifier? I know that there is one already existing for next resource (thanks DU staff), maybe someone has modified that to work with accessions instead? We use a two part accession identifier, so that might throw a wrench into the situation as well. Thanks, Brian Thomas Electronic Records Specialist Texas State Library and Archives Commission 1201 Brazos Street Austin, TX 78701 PH: (512) 475-3374 e-mail: bthomas at tsl.texas.gov tsl.texas.gov [cid:image001.jpg at 01D029A2.37194C70] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5314 bytes Desc: image001.png URL: From bthomas at tsl.texas.gov Thu Jul 27 09:58:47 2017 From: bthomas at tsl.texas.gov (Brian Thomas) Date: Thu, 27 Jul 2017 13:58:47 +0000 Subject: [Archivesspace_Users_Group] Accessions plug-in for auto-numbering In-Reply-To: References: Message-ID: Thanks Mike, a useful option and a laugh. I needed both. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Rush, Michael Sent: Thursday, July 27, 2017 8:57 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Accessions plug-in for auto-numbering Brian, Disregarding your disregard, in case you need another option, you could check out the plugin we use at Yale for that very purpose: https://github.com/hudmol/aspace_yale_accessions. Best, Mike __________________________________ Michael Rush Assistant Head of the Manuscript Unit Beinecke Rare Book and Manuscript Library Yale University 203-432-8123 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Brian Thomas Sent: Thursday, July 27, 2017 6:44 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Accessions plug-in for auto-numbering Please disregard that last question. I found something (thanks again DU!) From: Brian Thomas Sent: Thursday, July 27, 2017 8:42 AM To: Archivesspace Users Group Subject: Accessions plug-in for auto-numbering Has anyone written a plug-in for auto-generation of the next available accession identifier? I know that there is one already existing for next resource (thanks DU staff), maybe someone has modified that to work with accessions instead? We use a two part accession identifier, so that might throw a wrench into the situation as well. Thanks, Brian Thomas Electronic Records Specialist Texas State Library and Archives Commission 1201 Brazos Street Austin, TX 78701 PH: (512) 475-3374 e-mail: bthomas at tsl.texas.gov tsl.texas.gov [cid:image001.jpg at 01D029A2.37194C70] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5314 bytes Desc: image001.png URL: From PGalligan at rockarch.org Fri Jul 28 19:07:47 2017 From: PGalligan at rockarch.org (Galligan, Patrick) Date: Fri, 28 Jul 2017 23:07:47 +0000 Subject: [Archivesspace_Users_Group] Travis CI and ArchivesSpace Message-ID: <6FECE980-B9F1-4B32-B5BB-FE1E41808F29@rockarch.org> Hey List, I?m pretty new to Continuous Integration and scripted testing, so I thought I?d email the list. Anyone using TravisCI to create automated tests and to integrate with their ArchivesSpace production? I?m trying to up our software deployment game and could use some tips and tricks if you have them. Let me know! Patrick Galligan Rockefeller Archive Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From j at minorscience.com Sat Jul 29 00:22:43 2017 From: j at minorscience.com (Jason Loeffler) Date: Sat, 29 Jul 2017 04:22:43 +0000 Subject: [Archivesspace_Users_Group] Travis CI and ArchivesSpace In-Reply-To: <6FECE980-B9F1-4B32-B5BB-FE1E41808F29@rockarch.org> References: <6FECE980-B9F1-4B32-B5BB-FE1E41808F29@rockarch.org> Message-ID: Hi Patrick, I use a CI test harness regularly with Drupal development. Are you looking to fork AS and customize your code base and deploy that or do you simply want to write tests for the existing production branch? -- Jason Loeffler Technology Consultant | The American Academy in Rome Minor Science | Application Development & Metadata Strategy Brooklyn, New York jason at minorscience.com (347) 405-0826 minorscience (Skype) _____________________________ From: Galligan, Patrick > Sent: Friday, July 28, 2017 16:07 Subject: [Archivesspace_Users_Group] Travis CI and ArchivesSpace To: Archivesspace Users Group > Hey List, I?m pretty new to Continuous Integration and scripted testing, so I thought I?d email the list. Anyone using TravisCI to create automated tests and to integrate with their ArchivesSpace production? I?m trying to up our software deployment game and could use some tips and tricks if you have them. Let me know! Patrick Galligan Rockefeller Archive Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From PGalligan at rockarch.org Sat Jul 29 01:15:36 2017 From: PGalligan at rockarch.org (Galligan, Patrick) Date: Sat, 29 Jul 2017 05:15:36 +0000 Subject: [Archivesspace_Users_Group] Travis CI and ArchivesSpace In-Reply-To: References: <6FECE980-B9F1-4B32-B5BB-FE1E41808F29@rockarch.org> Message-ID: <7087AE4C-5BFD-47E7-9DDE-8C94A206A4C9@rockarch.org> Jason, Cool! I?m thinking that we?d probably be forking AS based upon our own codebase because of some pretty minor local customizations that are set up as plugins. We have some things that change layouts, changes to exporters, etc., and we want to do our due diligence in making sure that we?re not unexpectedly breaking something with each new release. Thought we could do it through automated methods rather than checking each plugin by hand each time. -Patrick From: on behalf of Jason Loeffler Reply-To: Archivesspace Users Group Date: Friday, July 28, 2017 at 9:22 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Travis CI and ArchivesSpace Hi Patrick, I use a CI test harness regularly with Drupal development. Are you looking to fork AS and customize your code base and deploy that or do you simply want to write tests for the existing production branch? -- Jason Loeffler Technology Consultant | The American Academy in Rome Minor Science | Application Development & Metadata Strategy Brooklyn, New York jason at minorscience.com (347) 405-0826 minorscience (Skype) _____________________________ From: Galligan, Patrick > Sent: Friday, July 28, 2017 16:07 Subject: [Archivesspace_Users_Group] Travis CI and ArchivesSpace To: Archivesspace Users Group > Hey List, I?m pretty new to Continuous Integration and scripted testing, so I thought I?d email the list. Anyone using TravisCI to create automated tests and to integrate with their ArchivesSpace production? I?m trying to up our software deployment game and could use some tips and tricks if you have them. Let me know! Patrick Galligan Rockefeller Archive Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From esha at nyu.edu Sat Jul 29 13:16:28 2017 From: esha at nyu.edu (Esha Datta) Date: Sat, 29 Jul 2017 13:16:28 -0400 Subject: [Archivesspace_Users_Group] Travis CI and ArchivesSpace In-Reply-To: <6FECE980-B9F1-4B32-B5BB-FE1E41808F29@rockarch.org> References: <6FECE980-B9F1-4B32-B5BB-FE1E41808F29@rockarch.org> Message-ID: Hi Patrick, I have used TravisCI for my plugin work. Here's the travis file with a marcxml export plugin that I had created. Let me know if you have any more questions. Thanks. Esha Datta Senior Programmer/Analyst Bobst Library NYU On Jul 28, 2017 7:08 PM, "Galligan, Patrick" wrote: Hey List, I?m pretty new to Continuous Integration and scripted testing, so I thought I?d email the list. Anyone using TravisCI to create automated tests and to integrate with their ArchivesSpace production? I?m trying to up our software deployment game and could use some tips and tricks if you have them. Let me know! Patrick Galligan Rockefeller Archive Center _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From jane.labarbara at mail.wvu.edu Mon Jul 31 12:12:29 2017 From: jane.labarbara at mail.wvu.edu (Jane LaBarbara) Date: Mon, 31 Jul 2017 16:12:29 +0000 Subject: [Archivesspace_Users_Group] Script for connecting accessions to resources? Message-ID: All, Does anyone have a script I could use or modify to "relate" accession records to resource records? We migrated in our resource records, then our accession records, and we know which accessions are supposed to be related to which resources, but I'm hoping there is a way to make the connections via script rather than one by one. Thank you, Jane / Jane Metters LaBarbara Assistant Curator, West Virginia & Regional History Center West Virginia University Libraries (304) 293-0352 office jane.labarbara at mail.wvu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From ew8ff at virginia.edu Mon Jul 31 23:08:38 2017 From: ew8ff at virginia.edu (Wilkinson, Elizabeth (ew8ff)) Date: Tue, 1 Aug 2017 03:08:38 +0000 Subject: [Archivesspace_Users_Group] Barcodes at the folder level Message-ID: My apologies if this question has come up previously. We assign barcodes at the folder level for small collections and for oversize materials that are part of larger collections. These types of materials go into communal boxes and/or flat file drawers (top containers) that do not get barcoded. We were wondering where people are placing the barcodes in ASpace for their folders in these situations. Thanks. --Elizabeth