From christine.dibella at lyrasis.org Tue May 1 09:01:28 2018 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Tue, 1 May 2018 13:01:28 +0000 Subject: [Archivesspace_Users_Group] Oracle changing Java licensing In-Reply-To: References: Message-ID: Dear Matt, Thanks for bringing this up. I talked with our Tech Lead, Laney, and we discussed that we?ll likely be changing our releases to include OpenJDK, in conjunction with moving up to Java 9. We?ll be adding changing over to OpenJDK 9 to the roadmap (anticipated for fall 2018). Our hope is that there would be very little impact to the community, and that the move would be fairly seamless. 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 On Behalf Of Matthew Adair Sent: Wednesday, April 25, 2018 10:23 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Oracle changing Java licensing This came across another thread. Oracle is quietly introducing changes to the Java 8 license. After January 2019, updates will still be public but you will need a license for "business, commercial or production use". I admittedly don't know what the ramifications would be for ASpace, but I thought I would pass it along just in case. https://java.com/en/download/release_notice.jsp Matt ---- Matthew Adair Lead Archivist for Digitization [https://docs.google.com/uc?export=download&id=1ayfBXUcs3eNToXAhNVdFT4XlVUtE6iR_&revid=0Bw_nuz0O5gALMHZQQlVTbStwdzMvdXdoanYxZkhyNmZtNVBRPQ] Bentley Historical Library 1150 Beal Avenue Ann Arbor, Michigan 48109-2113 734-647-3537 www.bentley.umich.edu @UmichBentley -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 6608 bytes Desc: image001.jpg URL: From christine.dibella at lyrasis.org Tue May 1 09:09:11 2018 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Tue, 1 May 2018 13:09:11 +0000 Subject: [Archivesspace_Users_Group] Importing EAD3 in v2.2.1 In-Reply-To: References: <06599BED401FE24C9913BC368E1073853C413E02@PMAMSX2.pmant1.local> Message-ID: Hi Margaret and Trevor, Trevor is correct ? we have not yet added an EAD3 importer, and the documentation should be updated to reflect this. Thanks for the reminder, and apologies for the inconvenience. Depending on timing, the label/explanatory text in the background jobs part of the application should be as well. We do have on the roadmap work on the importers/exporters, including adding one for EAD3, and a contractor who?s current working with us on various related activities. At least some of this work is due for the release that we are aiming to come out at the end of May, so it may be that the functionality is added before the label gets changed. 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 On Behalf Of Trevor Thornton Sent: Thursday, April 26, 2018 9:00 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Importing EAD3 in v2.2.1 As far as I know, the EAD importer has not been updated to support EAD3, but this isn't mentioned in the documentation, which I assume was written before EAD3 was released and EAD3 export was added to AS. On Wed, Apr 25, 2018 at 2:54 PM, Huang, Margaret > wrote: Dear All, I am writing to see if anyone has tried re-importing EAD3 into ArchivesSpace. For a project, I am experimenting with adding some very granular data and would like to use EAD3 because of the @localtype attribute. I exported EAD3 from ArchivesSpace, did some modification, and then tried to import the EAD3 back into ArchivesSpace. While the EAD3 validated outside of ArchivesSpace, I keep receiving the following error message ?instances / 0 / sub_container / type_2: container 2 requires both a type and indicator,? despite clearly having both a type and indicator in the EAD3. Any insights or suggestions would be greatly appreciated! Thank you in advance for your time, Marge Huang Margaret Huang Digital Archivist t 215-684-7641 e margaret.huang at philamuseum.org Philadelphia Museum of Art PO Box 7646, Philadelphia, PA 19101-7646 www.philamuseum.org _______________________________________________ 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: image002.jpg Type: image/jpeg Size: 6608 bytes Desc: image002.jpg URL: From rneal at richmond.edu Tue May 1 10:39:42 2018 From: rneal at richmond.edu (Neal, Rick) Date: Tue, 1 May 2018 14:39:42 +0000 Subject: [Archivesspace_Users_Group] Test server / production server ArchivesSpace question. Message-ID: Good morning, I am having some ArchivesSpace issues and need some advice. I have a test instance and a production instance of ArchiveSpace. I use version 1.5.1 on both servers. I use mysql. I want to update the test server from the production server. A. I dumped the database with mysqld on the production server. B. I then ran backup.sh on the production server (thinking that I need the index) and got the OUTPUT below at the bottom. I did not get a zip file created. I have no idea what happened but I am concerned now that the backup.sh file did something besides simply failing to create a zip file for me to take over to the test sever. I am concerned that if I restart the service ArchiveSpace will fail. C. I took the database dump and ingested it on the test server. I stopped and restarted the archivesspace service. ArchivesSpace doesn't show up in the browser. I recovered from a VM backup and have no problems with the test server but of course it did not get updated. Questions: 1. How concerned should I be about item B above? I took the database dump so I have that but I don't know anything about whether the index is damaged or how to fix it if it is. Again I am concerned that ArchivesSpace will not come back up if I restart the service. 2. What is the proper process for updating a test instance? Thanks for your help Rick Neal University of Richmond OUTPUT [root at server scripts]# ./backup.sh --output /dir/backup-20180501.zip Loading ArchivesSpace configuration file from path: /dir1/archivesspace/config/config.rb Loading ArchivesSpace configuration file from path: /dir1/archivesspace/config/config.rb 2018-05-01 10:00:46 -0400: Writing backup to /dir/backup-20180501.zip INFO: Previous snapshot status: {"startTime"=>"Tue May 01 10:00:00 EDT 2018", "fileCount"=>42, "status"=>"success", "snapshotCompletedAt"=>"Tue May 01 10:00:00 EDT 2018", "snapshotName"=>nil}; snapshot: IOError: No such file or directory create at /dir1/archivesspace/gems/gems/jruby-jars-1.7.21/lib/jruby-stdlib-1.7.21.jar!/META-INF/jruby.home/lib/ruby/shared/tmpdir.rb:0 initialize19 at org/jruby/ext/tempfile/Tempfile.java:95 new at org/jruby/RubyIO.java:853 get_tempfile at /dir1/archivesspace/gems/gems/rubyzip-1.0.0/lib/zip/file.rb:410 on_success_replace at /dir1/archivesspace/gems/gems/rubyzip-1.0.0/lib/zip/file.rb:401 commit at /dir1/archivesspace/gems/gems/rubyzip-1.0.0/lib/zip/file.rb:294 close at /dir1/archivesspace/gems/gems/rubyzip-1.0.0/lib/zip/file.rb:322 open at /dir1/archivesspace/gems/gems/rubyzip-1.0.0/lib/zip/file.rb:100 __ensure__ at ../launcher/backup/lib/backup.rb:115 backup at ../launcher/backup/lib/backup.rb:111 main at ../launcher/backup/lib/backup.rb:150 (root) at ../launcher/backup/lib/backup.rb:154 -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at virginia.edu Tue May 1 11:10:03 2018 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Tue, 1 May 2018 15:10:03 +0000 Subject: [Archivesspace_Users_Group] Test server / production server ArchivesSpace question. In-Reply-To: References: Message-ID: <1A010A6F-E780-4298-A0B4-7E0C284DD048@virginia.edu> The mysqldump is sufficient to restore ArchivesSpace state. It will rebuild the solr indexes. That will take a bit longer, but I prefer to do a complete clean reindex when cloning production to test. ( There are a number of glitches where the first bit of advice is usually to trigger a reindex. ) The only other state information that isn?t in the mysql database is the log info for batch jobs, which is in the data/shared/job_files directories. If you?re going to want to access output from old batch processes, you need to copy those. Typically, I retain those files when updating ArchivesSpace on production, but I don?t copy them when cloning production to test. ? Steve Majewski > On May 1, 2018, at 10:39 AM, Neal, Rick wrote: > > Good morning, > > I am having some ArchivesSpace issues and need some advice. > > I have a test instance and a production instance of ArchiveSpace. > > I use version 1.5.1 on both servers. I use mysql. > > I want to update the test server from the production server. > > A. I dumped the database with mysqld on the production server. > > B. I then ran backup.sh on the production server (thinking that I need the index) and got the OUTPUT below at the bottom. I did not get a zip file created. I have no idea what happened but I am concerned now that the backup.sh file did something besides simply failing to create a zip file for me to take over to the test sever. I am concerned that if I restart the service ArchiveSpace will fail. > > C. I took the database dump and ingested it on the test server. I stopped and restarted the archivesspace service. ArchivesSpace doesn?t show up in the browser. I recovered from a VM backup and have no problems with the test server but of course it did not get updated. > > Questions: > 1. How concerned should I be about item B above? I took the database dump so I have that but I don?t know anything about whether the index is damaged or how to fix it if it is. Again I am concerned that ArchivesSpace will not come back up if I restart the service. > 2. What is the proper process for updating a test instance? > > Thanks for your help > > Rick Neal > University of Richmond > > > > OUTPUT > > [root at server scripts]# ./backup.sh --output /dir/backup-20180501.zip > Loading ArchivesSpace configuration file from path: /dir1/archivesspace/config/config.rb > Loading ArchivesSpace configuration file from path: /dir1/archivesspace/config/config.rb > 2018-05-01 10:00:46 -0400: Writing backup to /dir/backup-20180501.zip > INFO: Previous snapshot status: {"startTime"=>"Tue May 01 10:00:00 EDT 2018", "fileCount"=>42, "status"=>"success", "snapshotCompletedAt"=>"Tue May 01 10:00:00 EDT 2018", "snapshotName"=>nil}; snapshot: > IOError: No such file or directory > create at /dir1/archivesspace/gems/gems/jruby-jars-1.7.21/lib/jruby-stdlib-1.7.21.jar!/META-INF/jruby.home/lib/ruby/shared/tmpdir.rb:0 > initialize19 at org/jruby/ext/tempfile/Tempfile.java:95 > new at org/jruby/RubyIO.java:853 > get_tempfile at /dir1/archivesspace/gems/gems/rubyzip-1.0.0/lib/zip/file.rb:410 > on_success_replace at /dir1/archivesspace/gems/gems/rubyzip-1.0.0/lib/zip/file.rb:401 > commit at /dir1/archivesspace/gems/gems/rubyzip-1.0.0/lib/zip/file.rb:294 > close at /dir1/archivesspace/gems/gems/rubyzip-1.0.0/lib/zip/file.rb:322 > open at /dir1/archivesspace/gems/gems/rubyzip-1.0.0/lib/zip/file.rb:100 > __ensure__ at ../launcher/backup/lib/backup.rb:115 > backup at ../launcher/backup/lib/backup.rb:111 > main at ../launcher/backup/lib/backup.rb:150 > (root) at ../launcher/backup/lib/backup.rb:154 > _______________________________________________ > 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: smime.p7s Type: application/pkcs7-signature Size: 6091 bytes Desc: not available URL: From clobdel1 at swarthmore.edu Tue May 1 12:18:15 2018 From: clobdel1 at swarthmore.edu (Chelsea Lobdell) Date: Tue, 1 May 2018 12:18:15 -0400 Subject: [Archivesspace_Users_Group] Test server / production server ArchivesSpace question. In-Reply-To: <1A010A6F-E780-4298-A0B4-7E0C284DD048@virginia.edu> References: <1A010A6F-E780-4298-A0B4-7E0C284DD048@virginia.edu> Message-ID: Just chiming in and backing up what Steve is saying. If you are just sync'ing the live DB with the test DB there's no need to run a backup. You really only need to have backups when you are upgrading to a new version of the software. I would also start with a fresh index. For this I would stop the application, ingest the live DB dump into the test DB, drop the current index to force a complete re-index by using the following command: rm -rf /path/to/archivesspace/data/* And then restart the application. A re-index can take some time depending on how large your DB is. Ours typically runs 1-2 hours. - Chelsea *---------------* *Chelsea Lobdell* *Library Web Developer/ Swarthmore College* *clobdel1 at swarthmore.edu / (610)690-6818* On Tue, May 1, 2018 at 11:10 AM, Majewski, Steven Dennis (sdm7g) < sdm7g at virginia.edu> wrote: > > The mysqldump is sufficient to restore ArchivesSpace state. > It will rebuild the solr indexes. That will take a bit longer, but I > prefer to do a complete clean reindex when cloning production to test. ( > There are a number of glitches where the first bit of advice is usually to > trigger a reindex. ) > > The only other state information that isn?t in the mysql database is the > log info for batch jobs, which is in the data/shared/job_files directories. > If you?re going to want to access output from old batch processes, you need > to copy those. > Typically, I retain those files when updating ArchivesSpace on production, > but I don?t copy them when cloning production to test. > > ? Steve Majewski > > > > On May 1, 2018, at 10:39 AM, Neal, Rick wrote: > > Good morning, > > I am having some ArchivesSpace issues and need some advice. > > I have a test instance and a production instance of ArchiveSpace. > > I use version 1.5.1 on both servers. I use mysql. > > I want to update the test server from the production server. > > A. I dumped the database with mysqld on the production server. > > B. I then ran backup.sh on the production server (thinking that I > need the index) and got the OUTPUT below at the bottom. I did *not *get > a zip file created. I have no idea what happened but I am concerned now > that the backup.sh file did something besides simply failing to create a > zip file for me to take over to the test sever. I am concerned that if I > restart the service ArchiveSpace will fail. > > C. I took the database dump and ingested it on the test server. I > stopped and restarted the archivesspace service. ArchivesSpace doesn?t > show up in the browser. I recovered from a VM backup and have no problems > with the test server but of course it did not get updated. > > Questions: > 1. How concerned should I be about item B above? I took the > database dump so I have that but I don?t know anything about whether the > index is damaged or how to fix it if it is. Again I am concerned that > ArchivesSpace will not come back up if I restart the service. > 2. What is the proper process for updating a test instance? > > Thanks for your help > > Rick Neal > University of Richmond > > > > OUTPUT > > [root at server scripts]# ./backup.sh --output /dir/backup-20180501.zip > Loading ArchivesSpace configuration file from path: > /dir1/archivesspace/config/config.rb > Loading ArchivesSpace configuration file from path: > /dir1/archivesspace/config/config.rb > 2018-05-01 10:00:46 -0400: Writing backup to /dir/backup-20180501.zip > INFO: Previous snapshot status: {"startTime"=>"Tue May 01 10:00:00 EDT > 2018", "fileCount"=>42, "status"=>"success", "snapshotCompletedAt"=>"Tue > May 01 10:00:00 EDT 2018", "snapshotName"=>nil}; snapshot: > IOError: No such file or directory > create at /dir1/archivesspace/gems/gems/ > jruby-jars-1.7.21/lib/jruby-stdlib-1.7.21.jar!/META-INF/ > jruby.home/lib/ruby/shared/tmpdir.rb:0 > initialize19 at org/jruby/ext/tempfile/Tempfile.java:95 > new at org/jruby/RubyIO.java:853 > get_tempfile at /dir1/archivesspace/gems/gems/ > rubyzip-1.0.0/lib/zip/file.rb:410 > on_success_replace at /dir1/archivesspace/gems/gems/ > rubyzip-1.0.0/lib/zip/file.rb:401 > commit at /dir1/archivesspace/gems/gems/ > rubyzip-1.0.0/lib/zip/file.rb:294 > close at /dir1/archivesspace/gems/gems/ > rubyzip-1.0.0/lib/zip/file.rb:322 > open at /dir1/archivesspace/gems/gems/ > rubyzip-1.0.0/lib/zip/file.rb:100 > __ensure__ at ../launcher/backup/lib/backup.rb:115 > backup at ../launcher/backup/lib/backup.rb:111 > main at ../launcher/backup/lib/backup.rb:150 > (root) at ../launcher/backup/lib/backup.rb:154 > _______________________________________________ > 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 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From k.yee at northeastern.edu Tue May 1 16:55:39 2018 From: k.yee at northeastern.edu (Yee, Karl) Date: Tue, 1 May 2018 20:55:39 +0000 Subject: [Archivesspace_Users_Group] memory issues with reports in v2.3.0 Message-ID: <0B655F2F-39D1-4358-9F4B-574A3961907C@northeastern.edu> On March 1st 2018 Kevin Clair Kevin.Clair at du.edu wrote: Hello, I was curious if anyone else on the list had noticed that reports (and possibly other background jobs) are consuming more memory in v2.3.0 than in previous versions of ArchivesSpace. We?ve noticed that reports that worked for us in 2.2.1 are throwing ?GC overhead limit exceeded? errors since we upgraded. We don?t use any of the default reports; every report we have in our instance is here: https://github.com/duspeccoll/archivesspace_reports. I?m sharing the link in case it?s a problem with our reports, and there are ways I could write them to be more efficient. thanks! -k -------------- next part -------------- An HTML attachment was scrubbed... URL: Reply: Hi Kevin Yes, we?re having the same problem with our instance of ArchivesSpace ver 2.3 as well. Even with the ?canned? accession report. Like you, it?s throwing out ?GC overhead limit exceeded? errors in the log and the whole reporting process just hangs. The errors persists, even after we set ASPACE_JAVA_XMX="-Xmx2048m" within the archivesspace.sh script. Has anyone found a solution? Karl Yee Computer Services Coordinator | Northeastern University Libraries | Library Technology Group 360 Huntington Ave. Boston, MA 02115 | (617) 373-4904 | k.yee at northeastern.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From dsprouse at tsl.texas.gov Wed May 2 11:41:23 2018 From: dsprouse at tsl.texas.gov (Daniel Sprouse) Date: Wed, 2 May 2018 15:41:23 +0000 Subject: [Archivesspace_Users_Group] =?windows-1252?q?everyone_seems_to_be?= =?windows-1252?q?_seeing_these_=93GC_overhead_limit_exceeded=94_errors?= Message-ID: Yes, I had reported that issue Monday, but decided it was a probably java problem, and to set GCS in the archivesspace.sh script then saw that there are only three custom opts there for java. ( ASPACE_JAVA_XMX="-Xmx1024m" ASPACE_JAVA_XSS="-Xss2m" and ASPACE_JAVA_MAXPERMSIZE="-XX:MaxPermSize=256m" ) I am curious if the following changes can (or should) be made/added in archivesspace.sh: -XX:+UseG1GC -XX:G1ReservePercent=40 -XX:NewRatio=2 and am curious how exactly to implement them if they should in fact be made. Thanks Daniel Sprouse, Linux Administrator Texas State Library & Archives Commission G 19.01 tel: 512-463-5482 -------------- next part -------------- An HTML attachment was scrubbed... URL: From kws2126 at columbia.edu Thu May 3 11:54:27 2018 From: kws2126 at columbia.edu (Kevin W. Schlottmann) Date: Thu, 3 May 2018 11:54:27 -0400 Subject: [Archivesspace_Users_Group] External authority control in AS Message-ID: Dear ArchivesSpace community, Here at Columbia we are in the process of migrating our archival description to ArchivesSpace. Until now, the record-of-record has been a collection-level library catalog record. These records undergo regular authority control along with the rest of the catalog. We plan to have the AS record be the record-of-record for archives going forward, with a one-way export to the catalog, the discovery layer, aggregators, etc. We'd like to continue to have our records undergo authority control with the same external vendor that does the main catalog's bibliographic records. I've come across some scripts and projects [1][2][3], but I haven't heard of anyone doing this systematically yet. We're exploring a variety of workflows to export data, have it undergo authority control, and re-import the data, but before we get too far, I'd love to hear from anyone who has set up automated external authority control (or has explored doing so). Kevin [1] Manual authority control scripts https://github.com/ehanson8/archivesspace-api https://github.com/jhu-archives-and-manuscripts/ASpace_API_Workshop [2] Kansas authority control project http://connect.ala.org/files/Authority%20control%20for%20finding%20aids_0.pdf [3] UNLV's awesome plugins https://github.com/UNLV-Libraries/ArchivesSpace-authority-project -- Kevin Schlottmann Head of Archives Processing Rare Book & Manuscript Library Butler Library, Room 801 Columbia University 535 W. 114th St., New York, NY 10027 (212) 854-8483 // kws2126 at columbia.edu From lhocking at litchfieldhistoricalsociety.org Mon May 7 09:39:40 2018 From: lhocking at litchfieldhistoricalsociety.org (Linda Hocking) Date: Mon, 7 May 2018 13:39:40 +0000 Subject: [Archivesspace_Users_Group] Component Unique Identifiers In-Reply-To: <158194AC-758D-4C20-AFEA-222E96119241@virginia.edu> References: , <158194AC-758D-4C20-AFEA-222E96119241@virginia.edu> Message-ID: Steve, A belated thank you for this reply. We do not have on site support for database issues, but I sent it to our consultant who just had a chance to make the change you suggested. It shows the identifier for the particular thing I have highlighted, but doesn't show where it is within the hierarchy. For example: [cid:6d6cceff-1df9-43de-a233-e0dac14475b6] Instead of File--Folder 2, I would like it to say Series 2--Subseries 2--File-Folder 2. It does give the title for each of those in the blue bar, but it doesn't add the identifiers. Is it possible to add another line to get it to display this? Thanks for your help! Linda ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Majewski, Steven Dennis (sdm7g) Sent: Thursday, April 12, 2018 3:31 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Component Unique Identifiers If I understand what you want correctly: Copy public/app/views/shared/_idbadge.html.erb into plugins/local/public/views/shared/ ( assuming local plugins are enabled ) and add a line to display result.identifier, for example: $ diff -U 6 public/app/views/shared/_idbadge.html.erb plugins/local/public/views/shared/_idbadge.html.erb --- public/app/views/shared/_idbadge.html.erb 2018-04-12 14:59:32.000000000 -0400 +++ plugins/local/public/views/shared/_idbadge.html.erb 2018-04-12 14:59:20.000000000 -0400 @@ -17,12 +17,13 @@ <%= (props.fetch(:full,false)? '

' : '

').html_safe %> <% if !props.fetch(:full,false) %> <%== result.display_string %> <% else %> <%== result.display_string %> <% end %> +

<%= result.identifier %>

<%= (props.fetch(:full,false)? '' : '').html_safe %> Since that template is shared in several places, that will add the identifier to other resource listings as well. digital_object listing already shows identifier next to the badge, so it looks a bit redundant there. If that?s not what you want, then add some qualifier on result.primary_type. For archival_objects, identifier will display directly beneath the title in the ?Collection Organization? tab of the resource. ? Steve Majewski On Apr 12, 2018, at 10:18 AM, Linda Hocking > wrote: Good morning, We?ve just linked our ArchivesSpace instance to our website and are trying to move our users away from Archon. There?s one major hurdle. We migrated from Archon to ArchivesSpace with the first migration tool, and our only container instances are nonsensical records created by the import. In most cases, our intellectual description matches up with the physical location, which means if I can see the series number and folder number I can find the item. I?m hoping to find out whether we can somehow force the public interface to display the component unique identifiers which do not appear when I look at finding aids in the public interface (or in the staff interface without viewing the particular record). It?s going to be quite some time before I can modify every finding aid and add containers, so I?m hoping in the meantime there is a temporary fix that doesn?t require me logging into the staff interface (or going back to Archon) every time a patron requests something. I wonder whether other Archon users are having this problem, and would welcome any suggestions. Thank you! Linda Linda M. Hocking, CA Curator of Library & Archives Litchfield Historical Society P.O. Box 385 Litchfield, CT 06759 860-567-4501 http://www.litchfieldhistoricalsociety.org archivist at litchfieldhistoricalsociety.org eboardman.tumblr.com _______________________________________________ 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: pastedImage.png Type: image/png Size: 17681 bytes Desc: pastedImage.png URL: From Kevin.Clair at du.edu Tue May 8 08:40:28 2018 From: Kevin.Clair at du.edu (Kevin Clair) Date: Tue, 8 May 2018 12:40:28 +0000 Subject: [Archivesspace_Users_Group] jQuery plugin question Message-ID: <8F7E4DD6-A48F-4F5B-9F86-E9438204490F@du.edu> Hello! If there?s anyone on the list who has experience with extending the behavior of the jQuery functions in ArchivesSpace, would you mind pinging me off-list? I have a plugin question. A jQuandary, if you will. thanks! -k -------------- next part -------------- An HTML attachment was scrubbed... URL: From jjahern at upenn.edu Tue May 8 10:32:04 2018 From: jjahern at upenn.edu (Ahern, Joseph-James J.) Date: Tue, 8 May 2018 14:32:04 +0000 Subject: [Archivesspace_Users_Group] Background Job access Settings Message-ID: Good Morning, I hope this is a simple question that someone on the list might know. We started using ASpace this past month, and have set up the staff interfaces. In getting familiar with the program - I went to do an import of an EAD record using the "Create Background Job" function - however, that was not an option on the drop down menu under "Create." That being said - I figure that the staff member who set up the interface must not have set the permissions at the right level to allow access to that functionality; or did not select that as a functional option in overall setup. If anyone knows what needs to be "flipped" to allow access to create background job functionality, please let me know. Thanks, J. J. Ahern Joseph-James Ahern Senior Archivist University Archives 3401 Market Street, Suite 210 University of Pennsylvania Philadelphia, PA 19104-6320 215-898-5240 jjahern at pobox.upenn.edu www.archives.upenn.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From ludwigpossie at weber.edu Tue May 8 11:39:45 2018 From: ludwigpossie at weber.edu (Ludwig Possie) Date: Tue, 8 May 2018 09:39:45 -0600 Subject: [Archivesspace_Users_Group] Archivesspace Docker in Production Message-ID: I'm curious to know if there are users out there using Archivesspace Docker version in a production environment? I'm looking at running this version in a production environment, but was having issues tying mysql and archivesspace containers together since the --link is a legacy feature being removed. -- Ludwig Possi? Systems Admin Stewart Library Weber State University 801-626-8093 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.cooper at lyrasis.org Tue May 8 12:00:14 2018 From: mark.cooper at lyrasis.org (Mark Cooper) Date: Tue, 8 May 2018 16:00:14 +0000 Subject: [Archivesspace_Users_Group] Archivesspace Docker in Production In-Reply-To: References: Message-ID: Hi Ludwig, The LYRASIS aspace docker repos on GitHub and the Docker Hub are being phased out. We now maintain these directly with aspace: https://hub.docker.com/r/archivesspace/archivesspace/tags/ https://github.com/archivesspace/archivesspace/blob/master/README_DOCKER.md Best, Mark Mark Cooper Tech Lead, Hosting and Support LYRASIS On May 8, 2018, at 8:39 AM, Ludwig Possie > wrote: I'm curious to know if there are users out there using Archivesspace Docker version in a production environment? I'm looking at running this version in a production environment, but was having issues tying mysql and archivesspace containers together since the --link is a legacy feature being removed. -- Ludwig Possi? Systems Admin Stewart Library Weber State University 801-626-8093 _______________________________________________ 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 akroeger at unomaha.edu Tue May 8 13:15:23 2018 From: akroeger at unomaha.edu (Angela Kroeger) Date: Tue, 8 May 2018 17:15:23 +0000 Subject: [Archivesspace_Users_Group] Background Job access Settings In-Reply-To: References: Message-ID: Hi, J. J. You might be able to fix this under Manage User Access (hidden in a drop menu under the gear icon next to your repository name), where you'd edit the groups of the user who needs to do this process and add them to an existing group that has access to this process. If none of your groups have access to this process, then try under Manage Groups (also under the little gear icon). Edit an existing group or create a new group with the following options checked: - cancel an import job (optional--we don't have this checked, and I can run EAD imports just fine) - initiate import jobs (required) - create and run a background job (required) - cancel a background job (also optional, but helpful if your job gets hung up on an error) I'm not sure if there are other options that need to be checked. I presume the user already has the ability to create and edit records outside of background jobs. If I'm missing something, someone please correct me. Hope this helps! --Angela Angela Kroeger Archives and Special Collections Associate UNO Libraries | Criss Library 107 University of Nebraska at Omaha | unomaha.edu 402.554.4159 akroeger at unomaha.edu [Media:UniversityCommunications:Graphic Design:Brand tools:Logos- UNO:Vector files:Lock-up:Lockup-color on white backgrnd.eps] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5540 bytes Desc: image001.png URL: From Christine.Kim at lyrasis.org Wed May 9 13:28:52 2018 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Wed, 9 May 2018 17:28:52 +0000 Subject: [Archivesspace_Users_Group] Webinar Announcement: The Evolution of the Finding Aid: From Document to Data - May 16 Message-ID: The Evolution of the Finding Aid: From Document to Data When: Wednesday, May 16, 2018 Time: 1:00 p.m. - 2:00 p.m. ET (10:00 a.m. - 11:00 a.m. PT) Where: Webinar at http://lyrasis.adobeconnect.com/r9a9jsf5r3g5/ Dial-in only option: 888-354-0094 - Access code is 731627 No registration required. The session is limited to the first 100 participants. Please feel free to host a webinar viewing group. The webinar will be recorded and available for viewing at a later date. Webinar description: Do you find the data model of ArchivesSpace different than how you're used to thinking of finding aids, and you can't quite put your finger on why? Have you heard words like "normalized" and "atomized" and wondered how and why they apply to archival data? Do concepts built into ASpace, like archival objects and top containers, seem a bit too unfamiliar to build confidence in your understanding of them? These are some of the areas that will be explored as we trace the evolution of the finding aid from a static, singular document into a collection of linked data points. In this webinar, Valerie Addonizio will explain the ways that description, both legacy and new, has evolved, especially as it relates to the way information is stored and displayed in ArchivesSpace. A particular focus will be placed on the concepts underlying some of the less intuitive features of ASpace, such as archival objects and container modeling. Presenters: Valerie Addonizio (Description Management Archivist, Johns Hopkins University) is an archivist at Johns Hopkins University whose primary responsibility is managing and correcting legacy data and maintaining physical control for all archival holdings. She was tasked with migrating from Archivists' Toolkit to ArchivesSpace from 2015 to 2016. Prior experience at Princeton University Libraries introduced her to the atomization of EAD, and further eye-opening experiences with the ASpace API led her to develop an API training workshop with Lora Woodford. Valerie hopes to leverage her experience learning these concepts to help narrow the sometimes scary gap between archivists and the technologies they rely on. Who should attend: Everyone interested in learning how collection management and description has evolved throughout the profession and how the core features and functionalities in ArchivesSpace relate to that evolution. This webinar will be specifically geared to individuals navigating the change between legacy practices and evolving data models. Questions? Please contact Kim at christine.kim at lyrasis.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From harmeyna at purdue.edu Fri May 11 10:27:15 2018 From: harmeyna at purdue.edu (Harmeyer, Neal A) Date: Fri, 11 May 2018 14:27:15 +0000 Subject: [Archivesspace_Users_Group] Component Unique Identifiers In-Reply-To: References: , <158194AC-758D-4C20-AFEA-222E96119241@virginia.edu> Message-ID: <0b595e856f204139a65b7d756b8dae53@wppexc09.purdue.lcl> Good day Linda, Steve, and all, My archives has also been working with the Component Unique Identifier (CUI) following a migration from Archon. At Purdue, we have begun using the CUI in a similar manner to Linda's repository, manually entering the intellectual coordinates that reflect the place of the archival object in the intellectual hierarchy. The format we chose to enter is: Collection #, Series #, Sub-Series #, File #, Item#. Doing so allows our staff and users to understand immediately the collection or intellectual grouping a researcher is requesting-this has proven very helpful to distinguish like-named entries in disparate collections. As an example of use of CUIs at Purdue, see: https://archives.lib.purdue.edu/repositories/2/resources/72. It's easiest to view in the Collection Organization section as one scrolls down. Like Linda's example, we'd like to have this done programmatically, wherein the software can assign these coordinates immediately upon the creation/save or re-order of an archival object in the hierarchy. Would this functionality be best-served as a new plug-in? Or perhaps a new feature? Thank you for any thoughts, Neal -- Neal Harmeyer Digital Archivist Purdue University Archives and Special Collections harmeyna at purdue.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Linda Hocking Sent: Monday, May 7, 2018 9:40 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Component Unique Identifiers Steve, A belated thank you for this reply. We do not have on site support for database issues, but I sent it to our consultant who just had a chance to make the change you suggested. It shows the identifier for the particular thing I have highlighted, but doesn't show where it is within the hierarchy. For example: [cid:image001.png at 01D3E912.A1556E10] Instead of File--Folder 2, I would like it to say Series 2--Subseries 2--File-Folder 2. It does give the title for each of those in the blue bar, but it doesn't add the identifiers. Is it possible to add another line to get it to display this? Thanks for your help! Linda ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Majewski, Steven Dennis (sdm7g) > Sent: Thursday, April 12, 2018 3:31 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Component Unique Identifiers If I understand what you want correctly: Copy public/app/views/shared/_idbadge.html.erb into plugins/local/public/views/shared/ ( assuming local plugins are enabled ) and add a line to display result.identifier, for example: $ diff -U 6 public/app/views/shared/_idbadge.html.erb plugins/local/public/views/shared/_idbadge.html.erb --- public/app/views/shared/_idbadge.html.erb 2018-04-12 14:59:32.000000000 -0400 +++ plugins/local/public/views/shared/_idbadge.html.erb 2018-04-12 14:59:20.000000000 -0400 @@ -17,12 +17,13 @@ <%= (props.fetch(:full,false)? '

' : '

').html_safe %> <% if !props.fetch(:full,false) %> <%== result.display_string %> <% else %> <%== result.display_string %> <% end %> +

<%= result.identifier %>

<%= (props.fetch(:full,false)? '' : '').html_safe %> Since that template is shared in several places, that will add the identifier to other resource listings as well. digital_object listing already shows identifier next to the badge, so it looks a bit redundant there. If that's not what you want, then add some qualifier on result.primary_type. For archival_objects, identifier will display directly beneath the title in the 'Collection Organization' tab of the resource. - Steve Majewski On Apr 12, 2018, at 10:18 AM, Linda Hocking > wrote: Good morning, We've just linked our ArchivesSpace instance to our website and are trying to move our users away from Archon. There's one major hurdle. We migrated from Archon to ArchivesSpace with the first migration tool, and our only container instances are nonsensical records created by the import. In most cases, our intellectual description matches up with the physical location, which means if I can see the series number and folder number I can find the item. I'm hoping to find out whether we can somehow force the public interface to display the component unique identifiers which do not appear when I look at finding aids in the public interface (or in the staff interface without viewing the particular record). It's going to be quite some time before I can modify every finding aid and add containers, so I'm hoping in the meantime there is a temporary fix that doesn't require me logging into the staff interface (or going back to Archon) every time a patron requests something. I wonder whether other Archon users are having this problem, and would welcome any suggestions. Thank you! Linda Linda M. Hocking, CA Curator of Library & Archives Litchfield Historical Society P.O. Box 385 Litchfield, CT 06759 860-567-4501 http://www.litchfieldhistoricalsociety.org archivist at litchfieldhistoricalsociety.org eboardman.tumblr.com _______________________________________________ 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.png Type: image/png Size: 17681 bytes Desc: image001.png URL: From lmcphee at ucsd.edu Fri May 11 10:40:26 2018 From: lmcphee at ucsd.edu (McPhee, Laurel) Date: Fri, 11 May 2018 14:40:26 +0000 Subject: [Archivesspace_Users_Group] Printing accession records - ASpace Message-ID: Good morning all, I have a vague memory of an institution (perhaps Yale?) developing a plug-in that would allow ASpace accession records to print up tidily and in a reader-friendly format on one page, the way AT accession records used to print. But looking at the current list of plug-ins and scripts, I didn't see anything like this in current use. Has anyone solved the accession-record-printing problem, or is this something that can be considered as a requested feature for forthcoming versions? Thank you in advance if anyone can share solutions for this issue, or point me to their plug-in. Laurel McPhee Supervisory Archivist, Special Collections & Archives Program UC San Diego Library | * 858-534-5619 | * lmcphee at ucsd.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From michael.rush at yale.edu Fri May 11 15:27:01 2018 From: michael.rush at yale.edu (Rush, Michael) Date: Fri, 11 May 2018 19:27:01 +0000 Subject: [Archivesspace_Users_Group] Printing accession records - ASpace In-Reply-To: References: Message-ID: Laurel, Here's the plugin that adds the print CSS: https://github.com/YaleArchivesSpace/print Best, Mike From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of McPhee, Laurel Sent: Friday, May 11, 2018 10:40 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Printing accession records - ASpace Good morning all, I have a vague memory of an institution (perhaps Yale?) developing a plug-in that would allow ASpace accession records to print up tidily and in a reader-friendly format on one page, the way AT accession records used to print. But looking at the current list of plug-ins and scripts, I didn't see anything like this in current use. Has anyone solved the accession-record-printing problem, or is this something that can be considered as a requested feature for forthcoming versions? Thank you in advance if anyone can share solutions for this issue, or point me to their plug-in. Laurel McPhee Supervisory Archivist, Special Collections & Archives Program UC San Diego Library | * 858-534-5619 | * lmcphee at ucsd.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From VivianLea.Solek at Kofc.Org Mon May 14 08:49:28 2018 From: VivianLea.Solek at Kofc.Org (VivianLea.Solek at Kofc.Org) Date: Mon, 14 May 2018 08:49:28 -0400 Subject: [Archivesspace_Users_Group] Printing accession records - ASpace In-Reply-To: References: Message-ID: Good morning, Can someone please shoot me a sample of what the style sheet renders? I'd like to see the final product before asking my IT partner to install this. MANY thanks and have a great week. 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 "Rush, Michael" ---05/11/2018 03:27:20 PM---Laurel, Here's the plugin that adds the print CSS: https:]"Rush, Michael" ---05/11/2018 03:27:20 PM---Laurel, Here's the plugin that adds the print CSS: https://urldefense.proofpoint.com/v2/url?u=https- From: "Rush, Michael" To: Archivesspace Users Group , Date: 05/11/2018 03:27 PM Subject: Re: [Archivesspace_Users_Group] Printing accession records - ASpace Sent by: archivesspace_users_group-bounces at lyralists.lyrasis.org ________________________________ Laurel, Here?s the plugin that adds the print CSS: https://github.com/YaleArchivesSpace/print Best, Mike From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of McPhee, Laurel Sent: Friday, May 11, 2018 10:40 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Printing accession records - ASpace Good morning all, I have a vague memory of an institution (perhaps Yale?) developing a plug-in that would allow ASpace accession records to print up tidily and in a reader-friendly format on one page, the way AT accession records used to print. But looking at the current list of plug-ins and scripts, I didn?t see anything like this in current use. Has anyone solved the accession-record-printing problem, or is this something that can be considered as a requested feature for forthcoming versions? Thank you in advance if anyone can share solutions for this issue, or point me to their plug-in. Laurel McPhee Supervisory Archivist, Special Collections & Archives Program UC San Diego Library | ? 858-534-5619 | ? lmcphee at ucsd.edu _______________________________________________ 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=DwICAg&c=C90XguLnqhMT2ADRaOs3gQ&r=balEICFvGrVJ8Sr6vcdFtVtZaJWT42A5myJ4zXSQILc&m=GMZAF72mhME3aBO6o862T9jfEY0G3fwpm5-zOUmyCgM&s=8FCZSFhnmgc7BNArQ7ivNWdQzUiceEGeVPoYOY6G9SE&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 michael.rush at yale.edu Mon May 14 09:26:11 2018 From: michael.rush at yale.edu (Rush, Michael) Date: Mon, 14 May 2018 13:26:11 +0000 Subject: [Archivesspace_Users_Group] Printing accession records - ASpace In-Reply-To: References: Message-ID: VivianLea, Here?s a PDF showing how the printout looks. Mike 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: Monday, May 14, 2018 8:49 AM To: Archivesspace Users Group Cc: archivesspace_users_group-bounces at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] Printing accession records - ASpace Good morning, Can someone please shoot me a sample of what the style sheet renders? I'd like to see the final product before asking my IT partner to install this. MANY thanks and have a great week. 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 "Rush, Michael" ---05/11/2018 03:27:20 PM---Laurel, Here's the plugin that adds the print CSS: https:]"Rush, Michael" ---05/11/2018 03:27:20 PM---Laurel, Here's the plugin that adds the print CSS: https://urldefense.proofpoint.com/v2/url?u=https- From: "Rush, Michael" > To: Archivesspace Users Group >, Date: 05/11/2018 03:27 PM Subject: Re: [Archivesspace_Users_Group] Printing accession records - ASpace Sent by: archivesspace_users_group-bounces at lyralists.lyrasis.org ________________________________ Laurel, Here?s the plugin that adds the print CSS: https://github.com/YaleArchivesSpace/print Best, Mike From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of McPhee, Laurel Sent: Friday, May 11, 2018 10:40 AM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Printing accession records - ASpace Good morning all, I have a vague memory of an institution (perhaps Yale?) developing a plug-in that would allow ASpace accession records to print up tidily and in a reader-friendly format on one page, the way AT accession records used to print. But looking at the current list of plug-ins and scripts, I didn?t see anything like this in current use. Has anyone solved the accession-record-printing problem, or is this something that can be considered as a requested feature for forthcoming versions? Thank you in advance if anyone can share solutions for this issue, or point me to their plug-in. Laurel McPhee Supervisory Archivist, Special Collections & Archives Program UC San Diego Library | ? 858-534-5619 | ? lmcphee at ucsd.edu _______________________________________________ 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=DwICAg&c=C90XguLnqhMT2ADRaOs3gQ&r=balEICFvGrVJ8Sr6vcdFtVtZaJWT42A5myJ4zXSQILc&m=GMZAF72mhME3aBO6o862T9jfEY0G3fwpm5-zOUmyCgM&s=8FCZSFhnmgc7BNArQ7ivNWdQzUiceEGeVPoYOY6G9SE&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: -------------- next part -------------- A non-text attachment was scrubbed... Name: ArchivesSpace _ Accessions _ Bilbo Baggins papers.pdf Type: application/pdf Size: 79099 bytes Desc: ArchivesSpace _ Accessions _ Bilbo Baggins papers.pdf URL: From VivianLea.Solek at Kofc.Org Mon May 14 10:17:04 2018 From: VivianLea.Solek at Kofc.Org (VivianLea.Solek at Kofc.Org) Date: Mon, 14 May 2018 10:17:04 -0400 Subject: [Archivesspace_Users_Group] Printing accession records - ASpace In-Reply-To: References: Message-ID: Good morning Mike, Thank you VERY much! 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 "Rush, Michael" ---05/14/2018 09:28:27 AM---VivianLea, Here?s a PDF showing how the printout looks.]"Rush, Michael" ---05/14/2018 09:28:27 AM---VivianLea, Here?s a PDF showing how the printout looks. From: "Rush, Michael" To: "Archivesspace Users Group" , Date: 05/14/2018 09:28 AM Subject: Re: [Archivesspace_Users_Group] Printing accession records - ASpace Sent by: ________________________________ VivianLea, Here?s a PDF showing how the printout looks. Mike 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: Monday, May 14, 2018 8:49 AM To: Archivesspace Users Group Cc: archivesspace_users_group-bounces at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] Printing accession records - ASpace Good morning, Can someone please shoot me a sample of what the style sheet renders? I'd like to see the final product before asking my IT partner to install this. MANY thanks and have a great week. 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 "Rush, Michael" ---05/11/2018 03:27:20 PM---Laurel, Here's the plugin that adds the print CSS: https:]"Rush, Michael" ---05/11/2018 03:27:20 PM---Laurel, Here's the plugin that adds the print CSS: https://urldefense.proofpoint.com/v2/url?u=https- From: "Rush, Michael" > To: Archivesspace Users Group >, Date: 05/11/2018 03:27 PM Subject: Re: [Archivesspace_Users_Group] Printing accession records - ASpace Sent by: archivesspace_users_group-bounces at lyralists.lyrasis.org ________________________________ Laurel, Here?s the plugin that adds the print CSS: https://github.com/YaleArchivesSpace/print Best, Mike From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of McPhee, Laurel Sent: Friday, May 11, 2018 10:40 AM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Printing accession records - ASpace Good morning all, I have a vague memory of an institution (perhaps Yale?) developing a plug-in that would allow ASpace accession records to print up tidily and in a reader-friendly format on one page, the way AT accession records used to print. But looking at the current list of plug-ins and scripts, I didn?t see anything like this in current use. Has anyone solved the accession-record-printing problem, or is this something that can be considered as a requested feature for forthcoming versions? Thank you in advance if anyone can share solutions for this issue, or point me to their plug-in. Laurel McPhee Supervisory Archivist, Special Collections & Archives Program UC San Diego Library | ? 858-534-5619 | ? lmcphee at ucsd.edu _______________________________________________ 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=DwICAg&c=C90XguLnqhMT2ADRaOs3gQ&r=balEICFvGrVJ8Sr6vcdFtVtZaJWT42A5myJ4zXSQILc&m=GMZAF72mhME3aBO6o862T9jfEY0G3fwpm5-zOUmyCgM&s=8FCZSFhnmgc7BNArQ7ivNWdQzUiceEGeVPoYOY6G9SE&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. [attachment "ArchivesSpace _ Accessions _ Bilbo Baggins papers.pdf" deleted by VivianLea Solek/HomeOffice/KofC] _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group [attachment "image001.gif" deleted by VivianLea Solek/HomeOffice/KofC] 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 mkottman at ku.edu Mon May 14 14:21:25 2018 From: mkottman at ku.edu (Kottman, Miloche) Date: Mon, 14 May 2018 18:21:25 +0000 Subject: [Archivesspace_Users_Group] Component Unique Identifiers In-Reply-To: <0b595e856f204139a65b7d756b8dae53@wppexc09.purdue.lcl> References: , <158194AC-758D-4C20-AFEA-222E96119241@virginia.edu> <0b595e856f204139a65b7d756b8dae53@wppexc09.purdue.lcl> Message-ID: <8eef62f9298b4f42a63d3705c31eb884@ex13-ell-cr-15.home.ku.edu> Neal, Our institution shelves materials by size and we don?t shift collections to accommodate additions. This means that a collection can have multiple call numbers. We use the component unique identifier to indicate at which call number a particular box, folder or item is shelved at. Programmatically assigning identifiers as you suggest would likely negatively impact how we use this field, so, I suggest pursuing a plug-in ?. --Miloche . . . . . . . . . . . . . . . . . . . . . . . . . . . . Miloche Kottman Head of Cataloging and Archival Processing University of Kansas Libraries Lawrence, KS 66045 mkottman at ku.edu 785-864-3916 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Harmeyer, Neal A Sent: Friday, May 11, 2018 9:27 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Component Unique Identifiers Good day Linda, Steve, and all, My archives has also been working with the Component Unique Identifier (CUI) following a migration from Archon. At Purdue, we have begun using the CUI in a similar manner to Linda?s repository, manually entering the intellectual coordinates that reflect the place of the archival object in the intellectual hierarchy. The format we chose to enter is: Collection #, Series #, Sub-Series #, File #, Item#. Doing so allows our staff and users to understand immediately the collection or intellectual grouping a researcher is requesting?this has proven very helpful to distinguish like-named entries in disparate collections. As an example of use of CUIs at Purdue, see: https://archives.lib.purdue.edu/repositories/2/resources/72. It?s easiest to view in the Collection Organization section as one scrolls down. Like Linda?s example, we?d like to have this done programmatically, wherein the software can assign these coordinates immediately upon the creation/save or re-order of an archival object in the hierarchy. Would this functionality be best-served as a new plug-in? Or perhaps a new feature? Thank you for any thoughts, Neal -- Neal Harmeyer Digital Archivist Purdue University Archives and Special Collections harmeyna at purdue.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Linda Hocking Sent: Monday, May 7, 2018 9:40 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Component Unique Identifiers Steve, A belated thank you for this reply. We do not have on site support for database issues, but I sent it to our consultant who just had a chance to make the change you suggested. It shows the identifier for the particular thing I have highlighted, but doesn't show where it is within the hierarchy. For example: [cid:image001.png at 01D3EB86.06257720] Instead of File--Folder 2, I would like it to say Series 2--Subseries 2--File-Folder 2. It does give the title for each of those in the blue bar, but it doesn't add the identifiers. Is it possible to add another line to get it to display this? Thanks for your help! Linda ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Majewski, Steven Dennis (sdm7g) > Sent: Thursday, April 12, 2018 3:31 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Component Unique Identifiers If I understand what you want correctly: Copy public/app/views/shared/_idbadge.html.erb into plugins/local/public/views/shared/ ( assuming local plugins are enabled ) and add a line to display result.identifier, for example: $ diff -U 6 public/app/views/shared/_idbadge.html.erb plugins/local/public/views/shared/_idbadge.html.erb --- public/app/views/shared/_idbadge.html.erb 2018-04-12 14:59:32.000000000 -0400 +++ plugins/local/public/views/shared/_idbadge.html.erb 2018-04-12 14:59:20.000000000 -0400 @@ -17,12 +17,13 @@ <%= (props.fetch(:full,false)? '

' : '

').html_safe %> <% if !props.fetch(:full,false) %> <%== result.display_string %> <% else %> <%== result.display_string %> <% end %> +

<%= result.identifier %>

<%= (props.fetch(:full,false)? '' : '').html_safe %> Since that template is shared in several places, that will add the identifier to other resource listings as well. digital_object listing already shows identifier next to the badge, so it looks a bit redundant there. If that?s not what you want, then add some qualifier on result.primary_type. For archival_objects, identifier will display directly beneath the title in the ?Collection Organization? tab of the resource. ? Steve Majewski On Apr 12, 2018, at 10:18 AM, Linda Hocking > wrote: Good morning, We?ve just linked our ArchivesSpace instance to our website and are trying to move our users away from Archon. There?s one major hurdle. We migrated from Archon to ArchivesSpace with the first migration tool, and our only container instances are nonsensical records created by the import. In most cases, our intellectual description matches up with the physical location, which means if I can see the series number and folder number I can find the item. I?m hoping to find out whether we can somehow force the public interface to display the component unique identifiers which do not appear when I look at finding aids in the public interface (or in the staff interface without viewing the particular record). It?s going to be quite some time before I can modify every finding aid and add containers, so I?m hoping in the meantime there is a temporary fix that doesn?t require me logging into the staff interface (or going back to Archon) every time a patron requests something. I wonder whether other Archon users are having this problem, and would welcome any suggestions. Thank you! Linda Linda M. Hocking, CA Curator of Library & Archives Litchfield Historical Society P.O. Box 385 Litchfield, CT 06759 860-567-4501 http://www.litchfieldhistoricalsociety.org archivist at litchfieldhistoricalsociety.org eboardman.tumblr.com _______________________________________________ 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.png Type: image/png Size: 17681 bytes Desc: image001.png URL: From reesj at mail.nlm.nih.gov Tue May 15 11:06:22 2018 From: reesj at mail.nlm.nih.gov (Rees, John (NIH/NLM) [E]) Date: Tue, 15 May 2018 15:06:22 +0000 Subject: [Archivesspace_Users_Group] Advice for recording journal article information Message-ID: We're migrating some journal article metadata to ASpace and are seeking description advice. The original metadata schema nicely records articleTitle, journalTitle, issue, pagination in distinct elements. ASpace doesn't specifically offer the same granularity in either Resource or Digital Object Records and we're considering using Notes subrecords to concatenate journal/issue/pagination data - we're not sure if any are a best fit. We'd also like to consider downstream linked data use cases where granularity would facilitate automated ID matching. I'm wary of the User Defined option. Anyone tackled this or a similar issue? Thanks, John John P. Rees Archivist and Digital Resources Manager History of Medicine Division National Library of Medicine 301-827-4510 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jmarch at email.wcu.edu Tue May 15 11:24:01 2018 From: jmarch at email.wcu.edu (Joel Marchesoni) Date: Tue, 15 May 2018 15:24:01 +0000 Subject: [Archivesspace_Users_Group] RSS feed of recently added items Message-ID: Hello, Is there any way to get an RSS feed (or the like) from ArchivesSpace of recently added items? Thanks, Joel Marchesoni Tech Support Analyst Hunter Library at Western Carolina University 828-227-2860 http://www.wcu.edu/hunter-library/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From Christine.Kim at lyrasis.org Tue May 15 11:37:30 2018 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Tue, 15 May 2018 15:37:30 +0000 Subject: [Archivesspace_Users_Group] Webinar Announcement: The Evolution of the Finding Aid: From Document to Data - May 16 In-Reply-To: References: Message-ID: Reminder - Join us for a webinar on The Evolution of the Finding Aid: From Document to Data tomorrow, Wednesday, May 16! Details: http://archivesspace.org/archives/2896 From: archivesspace_uac-bounces at lyralists.lyrasis.org [mailto:archivesspace_uac-bounces at lyralists.lyrasis.org] On Behalf Of Christine Kim Sent: Wednesday, May 9, 2018 10:29 AM Subject: [Archivesspace_uac] Webinar Announcement: The Evolution of the Finding Aid: From Document to Data - May 16 The Evolution of the Finding Aid: From Document to Data When: Wednesday, May 16, 2018 Time: 1:00 p.m. - 2:00 p.m. ET (10:00 a.m. - 11:00 a.m. PT) Where: Webinar at http://lyrasis.adobeconnect.com/r9a9jsf5r3g5/ Dial-in only option: 888-354-0094 - Access code is 731627 No registration required. The session is limited to the first 100 participants. Please feel free to host a webinar viewing group. The webinar will be recorded and available for viewing at a later date. Webinar description: Do you find the data model of ArchivesSpace different than how you're used to thinking of finding aids, and you can't quite put your finger on why? Have you heard words like "normalized" and "atomized" and wondered how and why they apply to archival data? Do concepts built into ASpace, like archival objects and top containers, seem a bit too unfamiliar to build confidence in your understanding of them? These are some of the areas that will be explored as we trace the evolution of the finding aid from a static, singular document into a collection of linked data points. In this webinar, Valerie Addonizio will explain the ways that description, both legacy and new, has evolved, especially as it relates to the way information is stored and displayed in ArchivesSpace. A particular focus will be placed on the concepts underlying some of the less intuitive features of ASpace, such as archival objects and container modeling. Presenters: Valerie Addonizio (Description Management Archivist, Johns Hopkins University) is an archivist at Johns Hopkins University whose primary responsibility is managing and correcting legacy data and maintaining physical control for all archival holdings. She was tasked with migrating from Archivists' Toolkit to ArchivesSpace from 2015 to 2016. Prior experience at Princeton University Libraries introduced her to the atomization of EAD, and further eye-opening experiences with the ASpace API led her to develop an API training workshop with Lora Woodford. Valerie hopes to leverage her experience learning these concepts to help narrow the sometimes scary gap between archivists and the technologies they rely on. Who should attend: Everyone interested in learning how collection management and description has evolved throughout the profession and how the core features and functionalities in ArchivesSpace relate to that evolution. This webinar will be specifically geared to individuals navigating the change between legacy practices and evolving data models. Questions? Please contact Kim at christine.kim at lyrasis.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From Christine.Kim at lyrasis.org Tue May 15 11:39:09 2018 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Tue, 15 May 2018 15:39:09 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Open Community Call -- May 24 at 2pm ET (11am PT) Message-ID: Dear ArchivesSpace members, Please join us for our next community Zoom call on Thursday, May 24 at 2-3pm ET (11-noon PT). This is an opportunity to hear updates from each other and encourage group discussion. You will be able to join by either computer or phone. This is a space to surface news, ideas, and challenges. This might be an especially good chance to talk about non-technical questions or ideas that you weren?t quite sure about posting on the Users Group listserv but really would like help with from us or your peers. In an effort to be more organized, here is a pre-survey to help generate discussion topics prior to the call. Please submit your suggestions by Tuesday, May 22. https://goo.gl/forms/2qPHAGev9AqgdG723 Here are the details of joining the call: * Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/804518729 * Or iPhone one-tap : * US: +16468769923,,804518729# or +16699006833,,804518729# * Or Telephone? * Dial(for higher quality, dial a number based on your current location)? * US: +1 646 876 9923 or +1 669 900 6833 or +1 408 638 0968 * Meeting ID: 804 518 729 * International numbers available: https://zoom.us/zoomconference?m=-CnZdNUzB4VhAipYXVQs3X1IOX8LOfFC Please email Kim at christine.kim at lyrasis.org if you have any questions about the call. We look forward to ?seeing? you there! Best wishes, Kim Christine Kim ArchivesSpace Community Engagement Coordinator christine.kim at lyrasis.org 800.999.8558 x4820 404.592.4820 Skype: ckim.lyrasis -------------- next part -------------- An HTML attachment was scrubbed... URL: From Christine.Kim at lyrasis.org Tue May 15 14:08:18 2018 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Tue, 15 May 2018 18:08:18 +0000 Subject: [Archivesspace_Users_Group] FW: REST-protocol In-Reply-To: <7ff73b05-4460-f09a-2d7e-f91a2ccb2abb@ruerddevries.nl> References: <7ff73b05-4460-f09a-2d7e-f91a2ccb2abb@ruerddevries.nl> Message-ID: Forwarding on behalf of Ruerd de Vries. Would anyone be able to help answer this question? Thank you! -----Original Message----- From: Archiefbureau Ruerd de Vries [mailto:info at ruerddevries.nl] Sent: Tuesday, May 15, 2018 10:33 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: REST-protocol Hello, Since a short while we are using ArchivesSpace, and now we mayby want to make a connection with an edepotsolution called Strongroom. The provider of Strongroom asked us if AS is being supported by the?socalled REST-protocol. I have no idea -;) Can anyone tell if that is the case? Thanks! Greetings from the Netherlands, Ruerd de Vries From bthomas at tsl.texas.gov Tue May 15 14:40:37 2018 From: bthomas at tsl.texas.gov (Brian Thomas) Date: Tue, 15 May 2018 18:40:37 +0000 Subject: [Archivesspace_Users_Group] REST-protocol In-Reply-To: References: <7ff73b05-4460-f09a-2d7e-f91a2ccb2abb@ruerddevries.nl> Message-ID: Yes, it should be. You can point them to the API documentation here: http://archivesspace.github.io/archivesspace/api/ for confirmation that this is what they are referring to. Hope that help, Brian Thomas -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Christine Kim Sent: Tuesday, May 15, 2018 1:08 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] FW: REST-protocol Forwarding on behalf of Ruerd de Vries. Would anyone be able to help answer this question? Thank you! -----Original Message----- From: Archiefbureau Ruerd de Vries [mailto:info at ruerddevries.nl] Sent: Tuesday, May 15, 2018 10:33 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: REST-protocol Hello, Since a short while we are using ArchivesSpace, and now we mayby want to make a connection with an edepotsolution called Strongroom. The provider of Strongroom asked us if AS is being supported by the?socalled REST-protocol. I have no idea -;) Can anyone tell if that is the case? Thanks! Greetings from the Netherlands, Ruerd de Vries _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group&data=02%7C01%7Cbthomas%40tsl.texas.gov%7C4fead3a16fa9453be5a108d5ba8edbe3%7Ca4597bff9f384145a0334a2168399a5e%7C0%7C0%7C636620045172628085&sdata=sSOXLtv2KIuZJBOqqJoZ%2FJ%2FdWo0okA29yVwY36YkE64%3D&reserved=0 From bobbi_fox at harvard.edu Tue May 15 14:51:02 2018 From: bobbi_fox at harvard.edu (Fox, Bobbi) Date: Tue, 15 May 2018 18:51:02 +0000 Subject: [Archivesspace_Users_Group] REST-protocol In-Reply-To: References: <7ff73b05-4460-f09a-2d7e-f91a2ccb2abb@ruerddevries.nl> Message-ID: Just to clarify: Aspace *Supports* an API that follows the REST protocol. While some of the programming of Aspace is *supported by* that API, I don't believe all of it is. Ymmv, Bobbi -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Brian Thomas Sent: Tuesday, May 15, 2018 2:41 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] REST-protocol Yes, it should be. You can point them to the API documentation here: http://archivesspace.github.io/archivesspace/api/ for confirmation that this is what they are referring to. Hope that help, Brian Thomas -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Christine Kim Sent: Tuesday, May 15, 2018 1:08 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] FW: REST-protocol Forwarding on behalf of Ruerd de Vries. Would anyone be able to help answer this question? Thank you! -----Original Message----- From: Archiefbureau Ruerd de Vries [mailto:info at ruerddevries.nl] Sent: Tuesday, May 15, 2018 10:33 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: REST-protocol Hello, Since a short while we are using ArchivesSpace, and now we mayby want to make a connection with an edepotsolution called Strongroom. The provider of Strongroom asked us if AS is being supported by the?socalled REST-protocol. I have no idea -;) Can anyone tell if that is the case? Thanks! Greetings from the Netherlands, Ruerd de Vries _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group&data=02%7C01%7Cbthomas%40tsl.texas.gov%7C4fead3a16fa9453be5a108d5ba8edbe3%7Ca4597bff9f384145a0334a2168399a5e%7C0%7C0%7C636620045172628085&sdata=sSOXLtv2KIuZJBOqqJoZ%2FJ%2FdWo0okA29yVwY36YkE64%3D&reserved=0 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group From ccauste1 at swarthmore.edu Tue May 15 14:55:28 2018 From: ccauste1 at swarthmore.edu (Celia Caust-Ellenbogen) Date: Tue, 15 May 2018 14:55:28 -0400 Subject: [Archivesspace_Users_Group] Does the API endpoint for PDFs work? Message-ID: Hello all, Has anyone had luck using the API endpoint to print a PDF? I am getting blank PDFs that have appropriate bookmarks (different for each PDF I print, appropriate headings for the specific resource) but no text in the document. Am I doing this wrong or does the endpoint not work? I noticed the API documentation says "EAD" instead of "PDF" ([:GET] /repositories/:repo_id/resource_descriptions/:id.pdf Description: Get an EAD representation of a Resource) so I suspect this feature may not be fully developed. Thanks! Celia -- Celia Caust-Ellenbogen Friends Historical Library of Swarthmore College 610-328-8496 ccauste1 at swarthmore.edu she/her/hers -------------- next part -------------- An HTML attachment was scrubbed... URL: From seth.shaw at unlv.edu Tue May 15 15:05:41 2018 From: seth.shaw at unlv.edu (Seth Shaw) Date: Tue, 15 May 2018 12:05:41 -0700 Subject: [Archivesspace_Users_Group] Does the API endpoint for PDFs work? In-Reply-To: References: Message-ID: What version do you have running? PDF export via API broke with 2.2.0 but was fixed in 2.3.0. On Tue, May 15, 2018 at 11:55 AM, Celia Caust-Ellenbogen < ccauste1 at swarthmore.edu> wrote: > Hello all, > > Has anyone had luck using the API endpoint to print a PDF? I am getting > blank PDFs that have appropriate bookmarks (different for each PDF I print, > appropriate headings for the specific resource) but no text in the > document. Am I doing this wrong or does the endpoint not work? > > I noticed the API documentation says "EAD" instead of "PDF" ([:GET] > /repositories/:repo_id/resource_descriptions/:id.pdf Description: > Get an EAD representation of a Resource) so I suspect this feature may not > be fully developed. > > Thanks! > Celia > > -- > Celia Caust-Ellenbogen > Friends Historical Library of Swarthmore College > > 610-328-8496 > ccauste1 at swarthmore.edu > she/her/hers > > > > _______________________________________________ > 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 ccauste1 at swarthmore.edu Tue May 15 16:12:01 2018 From: ccauste1 at swarthmore.edu (Celia Caust-Ellenbogen) Date: Tue, 15 May 2018 16:12:01 -0400 Subject: [Archivesspace_Users_Group] Does the API endpoint for PDFs work? In-Reply-To: References: Message-ID: This is on 2.3.2. I can print PDFs manually from the PUI but when I try to automate printing via the API, I get these blank PDFs. I'm doing all this because I have a particular resource record that is mysteriously giving me an error message when I try to print a PDF from the PUI (this one: http://archives.tricolib.brynmawr.edu/repositories/9/resources/5678) and I am trying to understand what might be causing the problem. Thanks in advance for any advice or insight! On Tue, May 15, 2018 at 3:05 PM, Seth Shaw wrote: > What version do you have running? PDF export via API broke with 2.2.0 but > was fixed in 2.3.0. > > On Tue, May 15, 2018 at 11:55 AM, Celia Caust-Ellenbogen < > ccauste1 at swarthmore.edu> wrote: > >> Hello all, >> >> Has anyone had luck using the API endpoint to print a PDF? I am getting >> blank PDFs that have appropriate bookmarks (different for each PDF I print, >> appropriate headings for the specific resource) but no text in the >> document. Am I doing this wrong or does the endpoint not work? >> >> I noticed the API documentation says "EAD" instead of "PDF" ([:GET] >> /repositories/:repo_id/resource_descriptions/:id.pdf Description: >> Get an EAD representation of a Resource) so I suspect this feature may not >> be fully developed. >> >> Thanks! >> Celia >> >> -- >> Celia Caust-Ellenbogen >> Friends Historical Library of Swarthmore College >> >> 610-328-8496 >> ccauste1 at swarthmore.edu >> she/her/hers >> >> >> >> _______________________________________________ >> 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 > > -- Celia Caust-Ellenbogen Friends Historical Library of Swarthmore College 610-328-8496 ccauste1 at swarthmore.edu she/her/hers -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at virginia.edu Tue May 15 16:19:41 2018 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Tue, 15 May 2018 20:19:41 +0000 Subject: [Archivesspace_Users_Group] Does the API endpoint for PDFs work? In-Reply-To: References: Message-ID: Try exporting the EAD and validating. There are still some cases where it exports malformed XML in some cases where these is mixed content in a note. The staff PDF export, first exports EAD which then goes to the as-ead-pdf.xsl stylesheet and then to the FOP processor. Feeding badly formed XML to the stylesheet will fail, and the error messages don?t seem to be caught. ? Steve. > On May 15, 2018, at 4:12 PM, Celia Caust-Ellenbogen wrote: > > This is on 2.3.2. I can print PDFs manually from the PUI but when I try to automate printing via the API, I get these blank PDFs. > > I'm doing all this because I have a particular resource record that is mysteriously giving me an error message when I try to print a PDF from the PUI (this one: http://archives.tricolib.brynmawr.edu/repositories/9/resources/5678 ) and I am trying to understand what might be causing the problem. > > Thanks in advance for any advice or insight! > > On Tue, May 15, 2018 at 3:05 PM, Seth Shaw > wrote: > What version do you have running? PDF export via API broke with 2.2.0 but was fixed in 2.3.0. > > On Tue, May 15, 2018 at 11:55 AM, Celia Caust-Ellenbogen > wrote: > Hello all, > > Has anyone had luck using the API endpoint to print a PDF? I am getting blank PDFs that have appropriate bookmarks (different for each PDF I print, appropriate headings for the specific resource) but no text in the document. Am I doing this wrong or does the endpoint not work? > > I noticed the API documentation says "EAD" instead of "PDF" ([:GET] /repositories/:repo_id/resource_descriptions/:id.pdf Description: Get an EAD representation of a Resource) so I suspect this feature may not be fully developed. > > Thanks! > Celia > > -- > Celia Caust-Ellenbogen > Friends Historical Library of Swarthmore College > 610-328-8496 > ccauste1 at swarthmore.edu > she/her/hers > > > > _______________________________________________ > 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 > > > > > -- > Celia Caust-Ellenbogen > Friends Historical Library of Swarthmore College > 610-328-8496 > ccauste1 at swarthmore.edu > she/her/hers > > > _______________________________________________ > 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: smime.p7s Type: application/pkcs7-signature Size: 6091 bytes Desc: not available URL: From ccauste1 at swarthmore.edu Wed May 16 11:51:16 2018 From: ccauste1 at swarthmore.edu (Celia Caust-Ellenbogen) Date: Wed, 16 May 2018 11:51:16 -0400 Subject: [Archivesspace_Users_Group] Does the API endpoint for PDFs work? In-Reply-To: References: Message-ID: Thanks, Steve, for the tip! Validating the EAD showed me an unescaped ampersand that was causing the problem. I'm worried there might be more culprits like this lurking in our database...does anyone know of an existing script to check for rogue unencoded special characters? And I am still curious about the API endpoint for EAD...has anyone used this successfully? Is the problem specific to me or should I create a JIRA ticket? On Tue, May 15, 2018 at 4:19 PM, Majewski, Steven Dennis (sdm7g) < sdm7g at virginia.edu> wrote: > Try exporting the EAD and validating. > There are still some cases where it exports malformed XML in some cases > where these is mixed content in a note. > The staff PDF export, first exports EAD which then goes to the > as-ead-pdf.xsl stylesheet and then to the FOP processor. > Feeding badly formed XML to the stylesheet will fail, and the error > messages don?t seem to be caught. > > ? Steve. > > > > On May 15, 2018, at 4:12 PM, Celia Caust-Ellenbogen < > ccauste1 at swarthmore.edu> wrote: > > This is on 2.3.2. I can print PDFs manually from the PUI but when I try to > automate printing via the API, I get these blank PDFs. > > I'm doing all this because I have a particular resource record that is > mysteriously giving me an error message when I try to print a PDF from the > PUI (this one: http://archives.tricolib.brynmawr.edu/repositories/9/ > resources/5678) and I am trying to understand what might be causing the > problem. > > Thanks in advance for any advice or insight! > > On Tue, May 15, 2018 at 3:05 PM, Seth Shaw wrote: > >> What version do you have running? PDF export via API broke with 2.2.0 but >> was fixed in 2.3.0. >> >> On Tue, May 15, 2018 at 11:55 AM, Celia Caust-Ellenbogen < >> ccauste1 at swarthmore.edu> wrote: >> >>> Hello all, >>> >>> Has anyone had luck using the API endpoint to print a PDF? I am getting >>> blank PDFs that have appropriate bookmarks (different for each PDF I print, >>> appropriate headings for the specific resource) but no text in the >>> document. Am I doing this wrong or does the endpoint not work? >>> >>> I noticed the API documentation says "EAD" instead of "PDF" ([:GET] >>> /repositories/:repo_id/resource_descriptions/:id.pdf >>> Description: Get an EAD representation of a Resource) so I suspect this >>> feature may not be fully developed. >>> >>> Thanks! >>> Celia >>> >>> -- >>> Celia Caust-Ellenbogen >>> Friends Historical Library of Swarthmore College >>> >>> 610-328-8496 >>> ccauste1 at swarthmore.edu >>> she/her/hers >>> >>> >>> >>> _______________________________________________ >>> 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 >> >> > > > -- > Celia Caust-Ellenbogen > Friends Historical Library of Swarthmore College > > 610-328-8496 > ccauste1 at swarthmore.edu > she/her/hers > > > _______________________________________________ > 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 > > -- Celia Caust-Ellenbogen Friends Historical Library of Swarthmore College 610-328-8496 ccauste1 at swarthmore.edu she/her/hers -------------- next part -------------- An HTML attachment was scrubbed... URL: From seth.shaw at unlv.edu Wed May 16 12:11:50 2018 From: seth.shaw at unlv.edu (Seth Shaw) Date: Wed, 16 May 2018 09:11:50 -0700 Subject: [Archivesspace_Users_Group] Does the API endpoint for PDFs work? In-Reply-To: References: Message-ID: We use the API to download PDFs for our website on a regular basis (since we don't use the PUI) using a script I wrote ( https://github.com/seth-shaw-unlv/small-stuff/blob/master/as-coll-mint/as_coll_mint.py). See line 210 ( https://github.com/seth-shaw-unlv/small-stuff/blob/31db6018bca18e9294b15db8094c8e4b8773a4f8/as-coll-mint/as_coll_mint.py#L210 ). On Wed, May 16, 2018 at 8:51 AM, Celia Caust-Ellenbogen < ccauste1 at swarthmore.edu> wrote: > Thanks, Steve, for the tip! Validating the EAD showed me an unescaped > ampersand that was causing the problem. > > I'm worried there might be more culprits like this lurking in our > database...does anyone know of an existing script to check for rogue > unencoded special characters? > > And I am still curious about the API endpoint for EAD...has anyone used > this successfully? Is the problem specific to me or should I create a JIRA > ticket? > > On Tue, May 15, 2018 at 4:19 PM, Majewski, Steven Dennis (sdm7g) < > sdm7g at virginia.edu> wrote: > >> Try exporting the EAD and validating. >> There are still some cases where it exports malformed XML in some cases >> where these is mixed content in a note. >> The staff PDF export, first exports EAD which then goes to the >> as-ead-pdf.xsl stylesheet and then to the FOP processor. >> Feeding badly formed XML to the stylesheet will fail, and the error >> messages don?t seem to be caught. >> >> ? Steve. >> >> >> >> On May 15, 2018, at 4:12 PM, Celia Caust-Ellenbogen < >> ccauste1 at swarthmore.edu> wrote: >> >> This is on 2.3.2. I can print PDFs manually from the PUI but when I try >> to automate printing via the API, I get these blank PDFs. >> >> I'm doing all this because I have a particular resource record that is >> mysteriously giving me an error message when I try to print a PDF from the >> PUI (this one: http://archives.tricolib.brynmawr.edu/repositories/9/re >> sources/5678) and I am trying to understand what might be causing the >> problem. >> >> Thanks in advance for any advice or insight! >> >> On Tue, May 15, 2018 at 3:05 PM, Seth Shaw wrote: >> >>> What version do you have running? PDF export via API broke with 2.2.0 >>> but was fixed in 2.3.0. >>> >>> On Tue, May 15, 2018 at 11:55 AM, Celia Caust-Ellenbogen < >>> ccauste1 at swarthmore.edu> wrote: >>> >>>> Hello all, >>>> >>>> Has anyone had luck using the API endpoint to print a PDF? I am getting >>>> blank PDFs that have appropriate bookmarks (different for each PDF I print, >>>> appropriate headings for the specific resource) but no text in the >>>> document. Am I doing this wrong or does the endpoint not work? >>>> >>>> I noticed the API documentation says "EAD" instead of "PDF" ([:GET] >>>> /repositories/:repo_id/resource_descriptions/:id.pdf >>>> Description: Get an EAD representation of a Resource) so I suspect this >>>> feature may not be fully developed. >>>> >>>> Thanks! >>>> Celia >>>> >>>> -- >>>> Celia Caust-Ellenbogen >>>> Friends Historical Library of Swarthmore College >>>> >>>> 610-328-8496 >>>> ccauste1 at swarthmore.edu >>>> she/her/hers >>>> >>>> >>>> >>>> _______________________________________________ >>>> 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 >>> >>> >> >> >> -- >> Celia Caust-Ellenbogen >> Friends Historical Library of Swarthmore College >> >> 610-328-8496 >> ccauste1 at swarthmore.edu >> she/her/hers >> >> >> _______________________________________________ >> 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 >> >> > > > -- > Celia Caust-Ellenbogen > Friends Historical Library of Swarthmore College > > 610-328-8496 > ccauste1 at swarthmore.edu > she/her/hers > > > > _______________________________________________ > 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 cbarber at amherst.edu Wed May 16 12:36:05 2018 From: cbarber at amherst.edu (Christina Barber) Date: Wed, 16 May 2018 16:36:05 +0000 Subject: [Archivesspace_Users_Group] Rapid Data Entry errors Message-ID: Hi all, Since upgrading to ArchivesSpace v. 2.3.2 from v. 1.5.3, we have encountered an error with Rapid Data Entry. Rapid Data Entry templates, both templates created in the new version and templates carried over from the previous version, are appearing - for lack of a better word - broken. Here are two screen shots of how our templates can appear in the Rapid Data Entry screen: occasionally with fields falling under incorrect elements (i.e. Label fields appearing under Date) or with a whole slew of other elements jumbled together without fields to edit, as in the first screen shot. These cause errors and an inability to save because some of the fields that are not appearing are required fields. Has anyone encountered a similar problem or have ideas about what's gone wrong? Our ArchivesSpace is hosted locally and managed by the College's IT department. Thanks, all, for any help, Chris Barber Christina E. Barber Deputy Archivist Amherst College cbarber at amherst.edu [cid:image001.jpg at 01D3ED12.4FCA0430] [cid:image002.png at 01D3ED12.4FCA0430] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 23038 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 25012 bytes Desc: image002.png URL: From sdm7g at virginia.edu Wed May 16 12:50:58 2018 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Wed, 16 May 2018 16:50:58 +0000 Subject: [Archivesspace_Users_Group] Does the API endpoint for PDFs work? In-Reply-To: References: Message-ID: <4B715C33-C99A-4BAF-A283-96898EBF584F@virginia.edu> > On May 16, 2018, at 11:51 AM, Celia Caust-Ellenbogen wrote: > > Thanks, Steve, for the tip! Validating the EAD showed me an unescaped ampersand that was causing the problem. > > I'm worried there might be more culprits like this lurking in our database...does anyone know of an existing script to check for rogue unencoded special characters? > > And I am still curious about the API endpoint for EAD...has anyone used this successfully? Is the problem specific to me or should I create a JIRA ticket? > Yes. I?ve been using it. All of the outstanding issues I?ve seen have been content dependent, and are due to that particular content producing malformed EAD that fails on the next step. It might be good to collect some examples of the different failure modes. Two others that I recall seeing ( unfortunately, I don?t have saved examples at hand, so just going by memory and missing some details) : If a note contains mixed content, like title or emphasis tags, especially if the tag begins an implicit paragraph, it can serialize the output with the tags overlapping rather than embedded. If a note or resource is marked published, but some inner note that is required to complete the EAD serialization is unpublished, and export unpublished is not selected, it can produce EAD that doesn?t validate due to the missing element. ( I really wish I could recall or reconstruct the exact elements that this occurred on! ) If you are trying to script PDF production using the API, it may be better to export EAD and and run the other steps ( validation, as-ead-pdf.xsl stylesheet, FOP processor ) in the script that is calling the ASpace API. ? Steve. > On Tue, May 15, 2018 at 4:19 PM, Majewski, Steven Dennis (sdm7g) > wrote: > Try exporting the EAD and validating. > There are still some cases where it exports malformed XML in some cases where these is mixed content in a note. > The staff PDF export, first exports EAD which then goes to the as-ead-pdf.xsl stylesheet and then to the FOP processor. > Feeding badly formed XML to the stylesheet will fail, and the error messages don?t seem to be caught. > > ? Steve. > > > >> On May 15, 2018, at 4:12 PM, Celia Caust-Ellenbogen > wrote: >> >> This is on 2.3.2. I can print PDFs manually from the PUI but when I try to automate printing via the API, I get these blank PDFs. >> >> I'm doing all this because I have a particular resource record that is mysteriously giving me an error message when I try to print a PDF from the PUI (this one: http://archives.tricolib.brynmawr.edu/repositories/9/resources/5678 ) and I am trying to understand what might be causing the problem. >> >> Thanks in advance for any advice or insight! >> >> On Tue, May 15, 2018 at 3:05 PM, Seth Shaw > wrote: >> What version do you have running? PDF export via API broke with 2.2.0 but was fixed in 2.3.0. >> >> On Tue, May 15, 2018 at 11:55 AM, Celia Caust-Ellenbogen > wrote: >> Hello all, >> >> Has anyone had luck using the API endpoint to print a PDF? I am getting blank PDFs that have appropriate bookmarks (different for each PDF I print, appropriate headings for the specific resource) but no text in the document. Am I doing this wrong or does the endpoint not work? >> >> I noticed the API documentation says "EAD" instead of "PDF" ([:GET] /repositories/:repo_id/resource_descriptions/:id.pdf Description: Get an EAD representation of a Resource) so I suspect this feature may not be fully developed. >> >> Thanks! >> Celia >> >> -- >> Celia Caust-Ellenbogen >> Friends Historical Library of Swarthmore College >> 610-328-8496 >> ccauste1 at swarthmore.edu >> she/her/hers >> >> >> >> _______________________________________________ >> 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 >> >> >> >> >> -- >> Celia Caust-Ellenbogen >> Friends Historical Library of Swarthmore College >> 610-328-8496 >> ccauste1 at swarthmore.edu >> she/her/hers >> >> >> _______________________________________________ >> 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 > > > > > -- > Celia Caust-Ellenbogen > Friends Historical Library of Swarthmore College > 610-328-8496 > ccauste1 at swarthmore.edu > she/her/hers > > > _______________________________________________ > 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: smime.p7s Type: application/pkcs7-signature Size: 6091 bytes Desc: not available URL: From benn.joseph at northwestern.edu Wed May 16 18:56:59 2018 From: benn.joseph at northwestern.edu (Benn Joseph) Date: Wed, 16 May 2018 22:56:59 +0000 Subject: [Archivesspace_Users_Group] Does the API endpoint for PDFs work? In-Reply-To: References: Message-ID: <8c3a23b2b5c64c34b893e9be06967dd5@evcspmbx04.ads.northwestern.edu> Hi Celia, Yes, we have a lot of records with unescaped ampersands?and unfortunately I?m not sure of any tools to check for those. Our plan was to compile a list of resource records that failed the staff PDF export, then export and validate the EAD for those to find the issues. That?s largely a manual process, which is why we haven?t done it yet. The other option we?re exploring is to create a standalone application that will pull data from the ArchivesSpace tables of a resource record and generate an .rtf document as a printable finding aid. This gives us some more leeway as far as manipulating the document?s look and feel, (since it?s hard to edit that PDF document in any meaningful way) as well as dictate what it includes (since the notes in our Agent records aren?t included in a collection?s staff-side PDF export). I can put you in touch with the staff member here who?s working on that effort if you?re interested. Ideally we wanted to be able to edit the PDF template that ArchivesSpace was using, and we still might try that, but we weren?t able to find enough documentation there to feel comfortable giving it a go. Best, --Benn Benn Joseph Head of Archival Processing Northwestern University Libraries Northwestern University www.library.northwestern.edu benn.joseph at northwestern.edu 847.467.6581 From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Celia Caust-Ellenbogen Sent: Wednesday, May 16, 2018 10:51 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Does the API endpoint for PDFs work? Thanks, Steve, for the tip! Validating the EAD showed me an unescaped ampersand that was causing the problem. I'm worried there might be more culprits like this lurking in our database...does anyone know of an existing script to check for rogue unencoded special characters? And I am still curious about the API endpoint for EAD...has anyone used this successfully? Is the problem specific to me or should I create a JIRA ticket? On Tue, May 15, 2018 at 4:19 PM, Majewski, Steven Dennis (sdm7g) > wrote: Try exporting the EAD and validating. There are still some cases where it exports malformed XML in some cases where these is mixed content in a note. The staff PDF export, first exports EAD which then goes to the as-ead-pdf.xsl stylesheet and then to the FOP processor. Feeding badly formed XML to the stylesheet will fail, and the error messages don?t seem to be caught. ? Steve. On May 15, 2018, at 4:12 PM, Celia Caust-Ellenbogen > wrote: This is on 2.3.2. I can print PDFs manually from the PUI but when I try to automate printing via the API, I get these blank PDFs. I'm doing all this because I have a particular resource record that is mysteriously giving me an error message when I try to print a PDF from the PUI (this one: http://archives.tricolib.brynmawr.edu/repositories/9/resources/5678) and I am trying to understand what might be causing the problem. Thanks in advance for any advice or insight! On Tue, May 15, 2018 at 3:05 PM, Seth Shaw > wrote: What version do you have running? PDF export via API broke with 2.2.0 but was fixed in 2.3.0. On Tue, May 15, 2018 at 11:55 AM, Celia Caust-Ellenbogen > wrote: Hello all, Has anyone had luck using the API endpoint to print a PDF? I am getting blank PDFs that have appropriate bookmarks (different for each PDF I print, appropriate headings for the specific resource) but no text in the document. Am I doing this wrong or does the endpoint not work? I noticed the API documentation says "EAD" instead of "PDF" ([:GET] /repositories/:repo_id/resource_descriptions/:id.pdf Description: Get an EAD representation of a Resource) so I suspect this feature may not be fully developed. Thanks! Celia -- Celia Caust-Ellenbogen Friends Historical Library of Swarthmore College 610-328-8496 ccauste1 at swarthmore.edu she/her/hers _______________________________________________ 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 -- Celia Caust-Ellenbogen Friends Historical Library of Swarthmore College 610-328-8496 ccauste1 at swarthmore.edu she/her/hers _______________________________________________ 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 -- Celia Caust-Ellenbogen Friends Historical Library of Swarthmore College 610-328-8496 ccauste1 at swarthmore.edu she/her/hers -------------- next part -------------- An HTML attachment was scrubbed... URL: From ltang5 at lib.msu.edu Wed May 16 21:13:16 2018 From: ltang5 at lib.msu.edu (Tang, Lydia) Date: Thu, 17 May 2018 01:13:16 +0000 Subject: [Archivesspace_Users_Group] Rapid Data Entry errors Message-ID: <7DE35B3E-7528-4DB0-8F8F-8FDF75B2E091@lib.msu.edu> Hi Chris, I just wanted to chime in and say that we experienced this as well. We ended up replacing our templates after the 2.x upgrade. Luckily, we didn?t have many specialized templates to update. Lydia From: on behalf of Christina Barber Reply-To: Archivesspace Users Group Date: Wednesday, May 16, 2018 at 12:36 PM To: "archivesspace_users_group at lyralists.lyrasis.org" Subject: [Archivesspace_Users_Group] Rapid Data Entry errors Hi all, Since upgrading to ArchivesSpace v. 2.3.2 from v. 1.5.3, we have encountered an error with Rapid Data Entry. Rapid Data Entry templates, both templates created in the new version and templates carried over from the previous version, are appearing ? for lack of a better word ? broken. Here are two screen shots of how our templates can appear in the Rapid Data Entry screen: occasionally with fields falling under incorrect elements (i.e. Label fields appearing under Date) or with a whole slew of other elements jumbled together without fields to edit, as in the first screen shot. These cause errors and an inability to save because some of the fields that are not appearing are required fields. Has anyone encountered a similar problem or have ideas about what?s gone wrong? Our ArchivesSpace is hosted locally and managed by the College?s IT department. Thanks, all, for any help, Chris Barber Christina E. Barber Deputy Archivist Amherst College cbarber at amherst.edu [cid:image001.jpg at 01D3ED12.4FCA0430] [cid:image002.png at 01D3ED12.4FCA0430] -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 23039 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 25013 bytes Desc: image002.png URL: From cory_nimer at byu.edu Thu May 17 11:46:39 2018 From: cory_nimer at byu.edu (Cory Nimer) Date: Thu, 17 May 2018 15:46:39 +0000 Subject: [Archivesspace_Users_Group] Request for comments: Language entry revisions Message-ID: <1526572000161.29307@byu.edu> Colleagues, In reviewing a series of bug reports and feature requests related to language entry in ArchivesSpace, the Development Prioritization Team has developed a comprehensive specification for potential updates to this functionality within the application. This document is available at https://docs.google.com/document/d/17arZyO-APS4o5RznSO251Bql4sPDW7Kg_BddkTZDJCs/edit?usp=sharing. Open issues addressed in the specification include: * ?ANW-144: MarcXML export is generating duplicate 040 field (https://archivesspace.atlassian.net/browse/ANW-144) * ANW-382: As an archivist, I would like to record finding aid Language of Description using controlled values (https://archivesspace.atlassian.net/browse/ANW-382) * ANW-697: As an archivist, I would like to record multiple Language entries using controlled terms (https://archivesspace.atlassian.net/browse/ANW-697) Comments related to the specification can be submitted through the Google Doc, or using the comment feature in the tickets in JIRA. Interested parties should also consider becoming a Watcher of the above issues. Questions about the specification document can also be directed to Cory Nimer (cory_nimer at byu.edu?). We would request that comments be submitted by May 31, 2018. Thank you, Cory Nimer University Archivist Brigham Young University 801-422-6091 -------------- next part -------------- An HTML attachment was scrubbed... URL: From kws2126 at columbia.edu Thu May 17 14:46:08 2018 From: kws2126 at columbia.edu (Kevin W. Schlottmann) Date: Thu, 17 May 2018 14:46:08 -0400 Subject: [Archivesspace_Users_Group] API security Message-ID: Dear AS Community, We are trying to make our AS instance secure before moving into production, and we are curious how institutions are securing their API. Right now, our calls are limited by IP range, and most (but not all for some reason) calls require authentication. Basically, we are looking for any thoughts on best practices for securing API access. We found this thread on security, but it is not quite on point for API access: http://lyralists.lyrasis.org/mailman/htdig/archivesspace_users_group/2016-February/003137.html Best, Kevin -- Kevin Schlottmann Head of Archives Processing Rare Book & Manuscript Library Butler Library, Room 801 Columbia University 535 W. 114th St., New York, NY 10027 (212) 854-8483 From Alston.Cobourn at tamucc.edu Thu May 17 14:54:30 2018 From: Alston.Cobourn at tamucc.edu (Cobourn, Alston) Date: Thu, 17 May 2018 18:54:30 +0000 Subject: [Archivesspace_Users_Group] OAI base urls containing port numbers Message-ID: We recently configured the OAI on our ArchivesSpace instance. By default our base url is http://archivesspace.tamucc.edu:8082/oai We are hoping to modify this base url so that does not contain the port number :8082 since that is a risk for hackers. Is there anyone who has an instance of ArchivesSpace maintained locally on your campus where you have modified the base url? If so, can you please send me info on how to modify the URL or put me in touch with the appropriate IT person at your institution? My IT guy is having a hard time figuring out how to make this change. Sincerely, Alston Cobourn Processing and Digital Assets Archivist Texas A&M-Corpus Christi Alston.cobourn at tamucc.edu 361-825-2300 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Kevin.Clair at du.edu Thu May 17 19:33:57 2018 From: Kevin.Clair at du.edu (Kevin Clair) Date: Thu, 17 May 2018 23:33:57 +0000 Subject: [Archivesspace_Users_Group] overriding default citation text in the PUI Message-ID: <6101199A-11CB-4D7D-B668-CC1AD27E6ED4@du.edu> Hello, We had a request here at the University of Denver to override the default formatting of citations in the PUI. It looks like the default is defined in public/app/models/resource.rb, which I haven?t been able to figure out how to override with a plugin. Has anyone extended the default behavior of these PUI models, and if so, can you provide some tips on how I could do so? thanks! -k -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.custer at yale.edu Thu May 17 21:10:18 2018 From: mark.custer at yale.edu (Custer, Mark) Date: Fri, 18 May 2018 01:10:18 +0000 Subject: [Archivesspace_Users_Group] overriding default citation text in the PUI In-Reply-To: <6101199A-11CB-4D7D-B668-CC1AD27E6ED4@du.edu> References: <6101199A-11CB-4D7D-B668-CC1AD27E6ED4@du.edu> Message-ID: Hopefully someone else can chime in with an actual answer about how to do this via a plugin, but outside of the views, I've had more success overriding things in the PUI with a custom build. And with the citation feature, you might also need to check out this bit, which is where the URL + timestamp text is added: https://github.com/archivesspace/archivesspace/blob/33a433f4df55c5ee4a21128825529bb9a1a4c023/public/app/models/record.rb#L331-L333 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Kevin Clair Sent: Thursday, May 17, 2018 7:33:57 PM To: Archivesspace Group Subject: [Archivesspace_Users_Group] overriding default citation text in the PUI Hello, We had a request here at the University of Denver to override the default formatting of citations in the PUI. It looks like the default is defined in public/app/models/resource.rb, which I haven?t been able to figure out how to override with a plugin. Has anyone extended the default behavior of these PUI models, and if so, can you provide some tips on how I could do so? thanks! -k -------------- next part -------------- An HTML attachment was scrubbed... URL: From lcalahan at umn.edu Fri May 18 08:33:45 2018 From: lcalahan at umn.edu (Lisa Calahan) Date: Fri, 18 May 2018 07:33:45 -0500 Subject: [Archivesspace_Users_Group] Rapid Data Entry errors In-Reply-To: <7DE35B3E-7528-4DB0-8F8F-8FDF75B2E091@lib.msu.edu> References: <7DE35B3E-7528-4DB0-8F8F-8FDF75B2E091@lib.msu.edu> Message-ID: We also had this problem. I ended up deleting the 20+ templates we had saved and creating new ones. On Wed, May 16, 2018 at 8:13 PM, Tang, Lydia wrote: > Hi Chris, > I just wanted to chime in and say that we experienced this as well. We > ended up replacing our templates after the 2.x upgrade. Luckily, we didn?t > have many specialized templates to update. > Lydia > > From: on behalf > of Christina Barber > Reply-To: Archivesspace Users Group lyralists.lyrasis.org> > Date: Wednesday, May 16, 2018 at 12:36 PM > To: "archivesspace_users_group at lyralists.lyrasis.org" < > archivesspace_users_group at lyralists.lyrasis.org> > Subject: [Archivesspace_Users_Group] Rapid Data Entry errors > > Hi all, > > Since upgrading to ArchivesSpace v. 2.3.2 from v. 1.5.3, we have > encountered an error with Rapid Data Entry. Rapid Data Entry templates, > both templates created in the new version and templates carried over from > the previous version, are appearing ? for lack of a better word ? broken. > Here are two screen shots of how our templates can appear in the Rapid Data > Entry screen: occasionally with fields falling under incorrect elements > (i.e. Label fields appearing under Date) or with a whole slew of other > elements jumbled together without fields to edit, as in the first screen > shot. These cause errors and an inability to save because some of the > fields that are not appearing are required fields. Has anyone encountered > a similar problem or have ideas about what?s gone wrong? Our ArchivesSpace > is hosted locally and managed by the College?s IT department. > > Thanks, all, for any help, > Chris Barber > > Christina E. Barber > Deputy Archivist > Amherst College > cbarber at amherst.edu > > [cid:image001.jpg at 01D3ED12.4FCA0430] > > [cid:image002.png at 01D3ED12.4FCA0430] > > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Pronouns: She/her/hers Head of Archival Processing University of Minnesota Libraries Archives and Special Collections Elmer L. Andersen Library, Suite 315 222-21st Ave. S. Minneapolis MN 55455 Phone: 612.626.2531 -------------- next part -------------- An HTML attachment was scrubbed... URL: From blake.carver at lyrasis.org Fri May 18 11:45:42 2018 From: blake.carver at lyrasis.org (Blake Carver) Date: Fri, 18 May 2018 15:45:42 +0000 Subject: [Archivesspace_Users_Group] OAI base urls containing port numbers In-Reply-To: References: Message-ID: Why is having a port number a risk for hackers? To drop the ports you'll probably need to run it behind nginx or Apache. The docs here explain how to run ArchivesSpace behind Apache: https://github.com/archivesspace/archivesspace/blob/master/README_HTTPS.md You can do the same thing with nginx. You don't need to use SSL, though it's a good idea. -Blake ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Cobourn, Alston Sent: Thursday, May 17, 2018 2:54:30 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] OAI base urls containing port numbers We recently configured the OAI on our ArchivesSpace instance. By default our base url is http://archivesspace.tamucc.edu:8082/oai We are hoping to modify this base url so that does not contain the port number :8082 since that is a risk for hackers. Is there anyone who has an instance of ArchivesSpace maintained locally on your campus where you have modified the base url? If so, can you please send me info on how to modify the URL or put me in touch with the appropriate IT person at your institution? My IT guy is having a hard time figuring out how to make this change. Sincerely, Alston Cobourn Processing and Digital Assets Archivist Texas A&M-Corpus Christi Alston.cobourn at tamucc.edu 361-825-2300 From Christine.Kim at lyrasis.org Fri May 18 13:00:25 2018 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Fri, 18 May 2018 17:00:25 +0000 Subject: [Archivesspace_Users_Group] Call for Lightning Round Speakers -- SoCal Regional Forum In-Reply-To: References: Message-ID: Happy Friday, everyone! Here's a quick program update on the SoCal Regional Forum, coming up on June 28th. The lightning round submission deadline has been extended to next Friday, May 25th! We welcome submissions that will represent diverse experiences and perspectives. Please submit any topics on current efforts, projects, initiatives, challenges, or ideas relating to collection management, access and discovery, implementation and migration, development, community participation, etc! More info here: http://archivesspace.org/archives/2884 Save the date for the ArchivesSpace Regional Forum in Southern California! Join us on June 28th for the SoCal Regional Forum hosted by the University of California, Irvine Libraries. The regional forums are opportunities for our diverse ArchivesSpace members to meet up more locally to share and learn from each other through workshops, focused discussion sessions, and presentations. Registration information will be sent out later next week. PROGRAM The specifics continue to be shaped by the working group. The most current information is available on the ArchivesSpace wiki. Morning Program: The morning session will highlight stories and experiences through presentations, discussions, and a lightning round. * Lightning round: Currently accepting submissions! More info here: http://archivesspace.org/archives/2884 Afternoon program: The afternoon session will feature a hands on, engaging activity or workshop selected by a community poll provided during registration. REGISTRATION Registration information will be sent out next week. QUESTIONS? If you have any questions (or ideas!) related to the regional forums, feel free to email Kim at christine.kim at lyrasis.org. Christine Kim ArchivesSpace Community Engagement Coordinator christine.kim at lyrasis.org 800.999.8558 x4820 404.592.4820 Skype: ckim.lyrasis From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Elvia Arroyo-Ramirez Sent: Thursday, April 19, 2018 3:03 PM To: Archivesspace Users Group ; Archivesspace Member Reps ; Archivesspace_tac at lyralists.lyrasis.org; Archivesspace_uac at lyralists.lyrasis.org; archivesspace_bot_members at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Call for Lightning Round Speakers -- SoCal Regional Forum Hello, The SoCal Regional Forum Working Group is seeking proposals for a lightning round of presentations, to be delivered at the ArchivesSpace SoCal Regional Forum at UC Irvine on June 28, 2018. The presentations will be capped at 5 minutes and topics can be on anything related to your work using, developing, implementing, or actively contributing to the ArchivesSpace application and community. Please use this form: https://goo.gl/forms/zowXsJvLWBPa0Bts1 to submit a short proposal (e.g. a topic, initiative, challenge, question, or program you are working on or thinking about) by Wednesday, May 23, 2018. You will receive a response by May 25, 2018. If you have any questions (or ideas) related to the lightning round submissions or the regional forums, feel free to email Kim at christine.kim at lyrasis.org. The regional forums are opportunities for our diverse ArchivesSpace members to meet up more locally to share and learn from each other through workshops, focused discussion sessions, and presentations. We look forward to having the content shaped by our community. Sincerely, Elvia Arroyo-Ramirez Margaret Hughes Christine Kim Kelly Spring Krystal Tribbett -------------- next part -------------- An HTML attachment was scrubbed... URL: From Christine.Kim at lyrasis.org Fri May 18 13:16:13 2018 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Fri, 18 May 2018 17:16:13 +0000 Subject: [Archivesspace_Users_Group] Webinar Announcement: The Evolution of the Finding Aid: From Document to Data - May 16 In-Reply-To: References: Message-ID: Just a quick announcement to share the recording and slides from this webinar have been posted! Links can be accessed through this post: http://archivesspace.org/archives/2910 Please let me know if you have any questions. Thanks, and have a great weekend! Christine Kim ArchivesSpace Community Engagement Coordinator christine.kim at lyrasis.org 800.999.8558 x4820 404.592.4820 Skype: ckim.lyrasis From: archivesspace_uac-bounces at lyralists.lyrasis.org [mailto:archivesspace_uac-bounces at lyralists.lyrasis.org] On Behalf Of Christine Kim Sent: Tuesday, May 15, 2018 8:38 AM To: Archivesspace Users Group ; Archivesspace Member Reps ; Archivesspace_tac at lyralists.lyrasis.org; Archivesspace_uac at lyralists.lyrasis.org; archivesspace_bot_members at lyralists.lyrasis.org Subject: Re: [Archivesspace_uac] Webinar Announcement: The Evolution of the Finding Aid: From Document to Data - May 16 Reminder - Join us for a webinar on The Evolution of the Finding Aid: From Document to Data tomorrow, Wednesday, May 16! Details: http://archivesspace.org/archives/2896 From: archivesspace_uac-bounces at lyralists.lyrasis.org [mailto:archivesspace_uac-bounces at lyralists.lyrasis.org] On Behalf Of Christine Kim Sent: Wednesday, May 9, 2018 10:29 AM Subject: [Archivesspace_uac] Webinar Announcement: The Evolution of the Finding Aid: From Document to Data - May 16 The Evolution of the Finding Aid: From Document to Data When: Wednesday, May 16, 2018 Time: 1:00 p.m. - 2:00 p.m. ET (10:00 a.m. - 11:00 a.m. PT) Where: Webinar at http://lyrasis.adobeconnect.com/r9a9jsf5r3g5/ Dial-in only option: 888-354-0094 - Access code is 731627 No registration required. The session is limited to the first 100 participants. Please feel free to host a webinar viewing group. The webinar will be recorded and available for viewing at a later date. Webinar description: Do you find the data model of ArchivesSpace different than how you're used to thinking of finding aids, and you can't quite put your finger on why? Have you heard words like "normalized" and "atomized" and wondered how and why they apply to archival data? Do concepts built into ASpace, like archival objects and top containers, seem a bit too unfamiliar to build confidence in your understanding of them? These are some of the areas that will be explored as we trace the evolution of the finding aid from a static, singular document into a collection of linked data points. In this webinar, Valerie Addonizio will explain the ways that description, both legacy and new, has evolved, especially as it relates to the way information is stored and displayed in ArchivesSpace. A particular focus will be placed on the concepts underlying some of the less intuitive features of ASpace, such as archival objects and container modeling. Presenters: Valerie Addonizio (Description Management Archivist, Johns Hopkins University) is an archivist at Johns Hopkins University whose primary responsibility is managing and correcting legacy data and maintaining physical control for all archival holdings. She was tasked with migrating from Archivists' Toolkit to ArchivesSpace from 2015 to 2016. Prior experience at Princeton University Libraries introduced her to the atomization of EAD, and further eye-opening experiences with the ASpace API led her to develop an API training workshop with Lora Woodford. Valerie hopes to leverage her experience learning these concepts to help narrow the sometimes scary gap between archivists and the technologies they rely on. Who should attend: Everyone interested in learning how collection management and description has evolved throughout the profession and how the core features and functionalities in ArchivesSpace relate to that evolution. This webinar will be specifically geared to individuals navigating the change between legacy practices and evolving data models. Questions? Please contact Kim at christine.kim at lyrasis.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From racheltrent at gwu.edu Mon May 21 15:46:08 2018 From: racheltrent at gwu.edu (Rachel Trent) Date: Mon, 21 May 2018 15:46:08 -0400 Subject: [Archivesspace_Users_Group] ASpace PUI: "Turning on/off" an entire type of record from public view Message-ID: Hi folks, Here's a feature/functionality question. For the PUI, what methods are available for excluding a type of record (say, all digital objects or all repositories) from public search results? In other words, is there an intended method for simply "switching on" and "switching off" an entire type of records from the search results? Here are some methods we have considered, using digital objects as an example (but you could also switch out "digital objects" for "accessions", "agents", "repositories", etc.): 1. *Remove the Digital Materials link from the main menu* -- Although this is easily configurable via the main config file, it wouldn't remove the digital object records from search results. So, it would be just a part of the solution. 2. *Unpublish all digital objects* -- This seems to be the most obvious solution, via the API. However, the digital objects are currently marked as published/unpublished in a meaningful way, and we'd rather not wipe that metadata. If we did choose this method, we would probably use the API to export a spreadsheet of the publish metadata, store that info outside of ASpace, and later use the API to import that metadata back in when we are ready to "turn on" the digital objects. (Also, this method wouldn't work for "turning off" repositories, because it would also turn off everything within the repositories.) 3. *Suppress all digital objects* -- This would preserve the publish metadata, but it would mean that most staff wouldn't be able to see or edit the suppressed records. Also, some types of entities (subjects, agents, repositories) can't be suppressed. 4. *Make configuration changes to Solr* -- Our goal is to keep customizations minimal and maintainable through migrations, so we'd like to stick with using the intended avenues of configuration (e.g., config file, plugins) and avoid any "off-menu" customizations/configurations. Thanks, Rachel Rachel Trent Digital Services Manager Special Collections Research Center Gelman Library, George Washington University 2130 H Street NW Washington DC 20052 202.994.4824 racheltrent at gwu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From susan.thomas at bodleian.ox.ac.uk Wed May 23 11:50:48 2018 From: susan.thomas at bodleian.ox.ac.uk (Susan Thomas) Date: Wed, 23 May 2018 15:50:48 +0000 Subject: [Archivesspace_Users_Group] Circulation of archives and manuscripts - options assessment Message-ID: Dear colleagues, We are in the process of implementing ArchivesSpace at the Bodleian Libraries for post-medieval archives and manuscripts. We also run a locally-built TEI infrastructure for medieval manuscripts, and for manuscripts in a range of Middle Eastern and Asian languages. One of our current priorities is exploring how we might introduce online ordering by patrons, and circulation. Ideally we would like to use the same approach for content described in ArchivesSpace and in TEI. The vast majority of circulation for archives and manuscripts is currently managed through paper slips (c. 30,000 requests p.a.), the exception being the growing proportion of material held in our offsite store (c. 5,000 requests p.a.). The offsite material (barcoded) is circulated by staff-mediated ordering through Ex Libris' Aleph, which hooks into GFA LAS (the software used to manage our offsite store). It would be very helpful to us to hear colleagues' views on the different possibilities, and especially to discover what have you chosen at your institution, and what options and considerations were weighed in the process. We are also considering some exploratory consultancy in this area, and would be keen to hear expressions of interest in such work, and recommendations of consultants with appropriate expertise. Feel free to respond to the list, or to email me directly. Many thanks for your help! Susan Susan Thomas Head of Archives & Modern Manuscripts Bodleian Library Web: http://www.bodleian.ox.ac.uk/special-collections Tel: +44 (0) 1865 283821 Post: Weston Library, Broad Street, Oxford, OX1 3BG -------------- next part -------------- An HTML attachment was scrubbed... URL: From Christine.Kim at lyrasis.org Wed May 23 13:05:37 2018 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Wed, 23 May 2018 17:05:37 +0000 Subject: [Archivesspace_Users_Group] [Archivesspace_tac] ArchivesSpace Open Community Call -- May 24 at 2pm ET (11am PT) In-Reply-To: References: Message-ID: Hello everyone, Just a friendly reminder to please join us for our open community call tomorrow, May 24 at 2pm ET (11am PT). Here is a loose agenda of topics up for discussion: https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/651264004/2018-05-24+Open+meeting+notes Thank you so much to those who submitted discussion topics in advance. No worries if you didn?t have a chance -- feel free to come with any topics you have in mind, and we?ll squeeze it all in! Here are some tips on setting up your audio and video, if joining by computer browser: https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/502693941/Setting+up+for+the+Open+Community+Calls. (If this is your first time using Zoom, we recommend joining at least 10 minutes ahead to get your browser set up.) And finally, call in information: https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/312868865/Open+Member+Zoom+Calls See you all tomorrow! Best wishes, Kim Christine Kim ArchivesSpace Community Engagement Coordinator christine.kim at lyrasis.org 800.999.8558 x4820 404.592.4820 Skype: ckim.lyrasis From: archivesspace_tac-bounces at lyralists.lyrasis.org [mailto:archivesspace_tac-bounces at lyralists.lyrasis.org] On Behalf Of Christine Kim Sent: Tuesday, May 15, 2018 8:39 AM To: Archivesspace Users Group ; Archivesspace Member Reps ; Archivesspace_uac at lyralists.lyrasis.org; Archivesspace_tac at lyralists.lyrasis.org; archivesspace_bot_members at lyralists.lyrasis.org Subject: [Archivesspace_tac] ArchivesSpace Open Community Call -- May 24 at 2pm ET (11am PT) Dear ArchivesSpace members, Please join us for our next community Zoom call on Thursday, May 24 at 2-3pm ET (11-noon PT). This is an opportunity to hear updates from each other and encourage group discussion. You will be able to join by either computer or phone. This is a space to surface news, ideas, and challenges. This might be an especially good chance to talk about non-technical questions or ideas that you weren?t quite sure about posting on the Users Group listserv but really would like help with from us or your peers. In an effort to be more organized, here is a pre-survey to help generate discussion topics prior to the call. Please submit your suggestions by Tuesday, May 22. https://goo.gl/forms/2qPHAGev9AqgdG723 Here are the details of joining the call: * Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/804518729 * Or iPhone one-tap : * US: +16468769923,,804518729# or +16699006833,,804518729# * Or Telephone? * Dial(for higher quality, dial a number based on your current location)? * US: +1 646 876 9923 or +1 669 900 6833 or +1 408 638 0968 * Meeting ID: 804 518 729 * International numbers available: https://zoom.us/zoomconference?m=-CnZdNUzB4VhAipYXVQs3X1IOX8LOfFC Please email Kim at christine.kim at lyrasis.org if you have any questions about the call. We look forward to ?seeing? you there! Best wishes, Kim Christine Kim ArchivesSpace Community Engagement Coordinator christine.kim at lyrasis.org 800.999.8558 x4820 404.592.4820 Skype: ckim.lyrasis -------------- next part -------------- An HTML attachment was scrubbed... URL: From brian.harrington at lyrasis.org Wed May 23 14:39:02 2018 From: brian.harrington at lyrasis.org (Brian Harrington) Date: Wed, 23 May 2018 18:39:02 +0000 Subject: [Archivesspace_Users_Group] EAD Importer and DAOs Message-ID: <29DC4117-373A-43E3-B1CC-0EB465FD76AB@lyrasis.org> Currently when importing an EAD, s are used to create digital objects. As part of this process, the @title attribute is used for both the digital object title, and the caption under file versions. I've recently run into a fun issue with s with @titles longer than 255 characters. These titles are OK for digital_object:title, which is VARCHAR(8704) but too long for file_version:caption, which is VARCHAR(255). So the import fails. Should this be considered a bug? If it is, and if one were theoretically considering a PR, would it make more sense to harmonize the length of the title and caption, or truncate the caption to 255 characters? My inclination is just to increase the maximum length of captions, and rely on people to show restraint, but I know that other people might have different opinions. Thanks, Brian -- Brian Harrington Migration Specialist LYRASIS brian.harrington at lyrasis.org skype: abbistani From ludwigpossie at weber.edu Wed May 23 19:16:30 2018 From: ludwigpossie at weber.edu (Ludwig Possie) Date: Wed, 23 May 2018 17:16:30 -0600 Subject: [Archivesspace_Users_Group] Archivesspace Docker in Production In-Reply-To: References: Message-ID: Mark; I'm trying to duplicate my production environment to a docker container. I managed to create my own custom image per the provided instructions. However it's running on the latest ArchivesSpace version. Our current production version is v2.0.1. I searched through the git commits on GitHub and went back to around the time 2.0.0 was out (65b0f5f1509d925f1da234f3edc7084687526818). I then copied over some of the Dockerfiles and docker-compose.yml files and ran the scripts. I'm still having to do some tinkering to see if I can get it to work properly, but just wanted to know if there was a better way for me to rebuild that image? Also is there any documentation with the recommended method of upgrading from one version to another when using Docker containers? Thx. Ludwig Poss? On Tue, May 8, 2018 at 10:00 AM, Mark Cooper wrote: > Hi Ludwig, > > The LYRASIS aspace docker repos on GitHub and the Docker Hub are being > phased out. We now maintain these directly with aspace: > > https://hub.docker.com/r/archivesspace/archivesspace/tags/ > https://github.com/archivesspace/archivesspace/ > blob/master/README_DOCKER.md > > Best, > Mark > > Mark Cooper > Tech Lead, Hosting and Support > LYRASIS > > On May 8, 2018, at 8:39 AM, Ludwig Possie wrote: > > I'm curious to know if there are users out there using Archivesspace > Docker version in a production environment? I'm looking at running this > version in a production > environment, but was having issues tying mysql and archivesspace containers > together since the --link is a legacy feature being removed. > > -- > Ludwig Possi? > Systems Admin > Stewart Library > Weber State University > 801-626-8093 > _______________________________________________ > 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 > > -- Ludwig Possi? Systems Admin Stewart Library Weber State University 801-626-8093 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Christine.Kim at lyrasis.org Wed May 23 21:14:25 2018 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Thu, 24 May 2018 01:14:25 +0000 Subject: [Archivesspace_Users_Group] ASpace SoCal Regional Forum - Registration is now open! Message-ID: Join us for the ArchivesSpace Regional Forum in Southern California! The regional forums are opportunities for our diverse ArchivesSpace members to meet up more locally to share and learn from each other through workshops, focused discussion sessions, and presentations. Registration is now open! [http://archivesspace.org/wp-content/uploads/2018/05/SoCal-Banner-2-1024x512.jpg] DETAILS * Location: UC Irvine, Student Center * Date: June 28, 2018 (Thursday) * Time: 9am - 5pm Parking: Parking & Transportation * PROGRAM The specifics continue to be shaped by the working group. The most current information is available on the ArchivesSpace wiki. * Morning Program: The morning session will highlight stories and experiences through presentations, discussions, and a lightning round. [Please note: We are currently accepting submissions for the lightning round! Submissions requested by May 31st. More info here: [http://archivesspace.org/archives/2843] * Afternoon program: The afternoon session will feature a hands on, engaging activity or workshop selected by a community poll provided during registration. [The poll will appear during check-out, and is available until June 5th. The activity will be selected soon after this date, and will be announced shortly after.] * Happy Hour: The day concludes with an optional happy hour at the Anthill Pub on campus. REGISTRATION Registration, including the afternoon session poll, is now open: https://www.eventbrite.com/e/archivesspace-regional-forum-southern-california-2018-tickets-44930947674 QUESTIONS? If you have any questions (or ideas!) related to the regional forums, feel free to email Kim at christine.kim at lyrasis.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 51613 bytes Desc: image003.jpg URL: From moconway at umich.edu Thu May 24 12:47:26 2018 From: moconway at umich.edu (Martha O'Hara Conway) Date: Thu, 24 May 2018 12:47:26 -0400 Subject: [Archivesspace_Users_Group] Now Available! Revised Draft Guidelines for Standardized Holdings Counts and Measures for Archival Repositories and Special Collections Libraries Message-ID: *On behalf of the SAA-ACRL/RBMS Joint Task Force on the Development of Standardized Holdings Counts and Measures for Archival Repositories and Special Collections Libraries, I am very pleased to announce the release of our revised draft Guidelines for Standardized Holdings Counts and Measures for Archival Repositories and Special Collections Libraries . The Guidelines are the product of the Task Force?s efforts to analyze and address feedback received in response to the draft we released on 11 January 2017, which is summarized in our July 20, 2017 Annual Report to the SAA Standards Committee. The Guidelines are available both online and as a PDF via this SAA website:https://www2.archivists.org/groups/saa-acrlrbms-joint-task-force-on-holdings-metrics/guidelines-for-standardized-holdings-counts-and-measures-for-archival-r The Guidelines reflect a multi-year effort to develop definitions and best practices for quantifying the holdings of archival repositories and special collections libraries. The Guidelines address both the wide range of types and formats of material typically held and the different ways collection material is managed and described. The Task Force invites comments on the revised draft. Please direct feedback to the co-chairs before Tuesday, July 31, 2018:Martha O?Hara Conway, moconway at umich.edu (for RBMS)Emily R. Novak Gustainis, emily_gustainis at hms.harvard.edu (for SAA) With thanks in advance for your interest and input, Martha, on behalf of the SAA-ACRL/RBMS Joint Task Force on the Development of Standardized Holdings Counts and Measures for Archival Repositories and Special Collections Libraries Martha O?Hara Conway (RBMS) University of Michigan, co-chairRachel A. D'Agostino (RBMS) Library Company of PhiladelphiaLara Friedman?Shedlov (RBMS) University of MinnesotaEmily R. Novak Gustainis (SAA) Harvard Medical School, co-chairE. Haven Hawley (RBMS) University of FloridaLisa K. Miller (SAA) Stanford University* ********************************************************************* Martha O'Hara Conway Director * Special Collections Research Center University of Michigan Library * Ann Arbor MI 48109-1190 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Christine.Kim at lyrasis.org Thu May 24 15:07:17 2018 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Thu, 24 May 2018 19:07:17 +0000 Subject: [Archivesspace_Users_Group] [Archivesspace_tac] ArchivesSpace Open Community Call -- May 24 at 2pm ET (11am PT) In-Reply-To: References: Message-ID: Hi everyone, Thank you all for participating in our open call today! Just a quick note to share the notes from today's call: https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/651264004/2018-05-24+Open+meeting+notes We will plan to schedule our next open community call in July. Thank you! Best wishes, Kim Christine Kim ArchivesSpace Community Engagement Coordinator christine.kim at lyrasis.org 800.999.8558 x4820 404.592.4820 Skype: ckim.lyrasis -------------- next part -------------- An HTML attachment was scrubbed... URL: From timmo at jhu.edu Thu May 24 17:25:43 2018 From: timmo at jhu.edu (Timothy Dilauro) Date: Thu, 24 May 2018 21:25:43 +0000 Subject: [Archivesspace_Users_Group] EAD Importer and DAOs In-Reply-To: <29DC4117-373A-43E3-B1CC-0EB465FD76AB@lyrasis.org> References: <29DC4117-373A-43E3-B1CC-0EB465FD76AB@lyrasis.org> Message-ID: <38BE6D72-437B-464E-92BF-3D73E4F9D2A3@jhu.edu> Hi Brian, I don't think it's a good idea to change the data model just to avoid imports failing, though there may be other rationales that result in such a change. In the mean time, it might be useful to write some XSLT or some other custom code to perform sanity checks relative to ASpace restrictions ahead of EAD import attempts. In that manner, those non-conformant captions (and anything else you check on) could be tweaked before import. Cheers, ~Tim > On May 23, 2018, at 2:39 PM, Brian Harrington wrote: > > > Currently when importing an EAD, s are used to create digital objects. As part of this process, the @title attribute is used for both the digital object title, and the caption under file versions. I've recently run into a fun issue with s with @titles longer than 255 characters. These titles are OK for digital_object:title, which is VARCHAR(8704) but too long for file_version:caption, which is VARCHAR(255). So the import fails. > > Should this be considered a bug? If it is, and if one were theoretically considering a PR, would it make more sense to harmonize the length of the title and caption, or truncate the caption to 255 characters? My inclination is just to increase the maximum length of captions, and rely on people to show restraint, but I know that other people might have different opinions. > > Thanks, > > Brian > > -- > Brian Harrington > Migration Specialist > LYRASIS > brian.harrington at lyrasis.org > skype: abbistani > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 235 bytes Desc: Message signed with OpenPGP URL: From brian.harrington at lyrasis.org Fri May 25 09:34:42 2018 From: brian.harrington at lyrasis.org (Brian Harrington) Date: Fri, 25 May 2018 13:34:42 +0000 Subject: [Archivesspace_Users_Group] EAD Importer and DAOs In-Reply-To: <38BE6D72-437B-464E-92BF-3D73E4F9D2A3@jhu.edu> References: <29DC4117-373A-43E3-B1CC-0EB465FD76AB@lyrasis.org> <38BE6D72-437B-464E-92BF-3D73E4F9D2A3@jhu.edu> Message-ID: <1EE5C4D0-ABF6-49D7-B456-4B81E5CF9044@lyrasis.org> Hi Tim, I agree it seems a bit backwards to change the data model to suit the importer, which is one of the reasons I decided to pose the question to the list. There could be valid reasons (display issues?) for limiting the length of the caption, but these things are often assigned somewhat arbitrarily, so I thought I would ask. If there are reasons for keeping for keeping the caption at 255, then I think it makes sense to truncate it in the importer, rather than just having things die on a database error. I currently use a modified version of Mark Custer?s schematron to check EADs prior to import, and can certainly add code to check @titles. The problem with doing that is the double use of @title for both digital_object:title and file_version:caption. Since ASpace supports long titles, and the archivist presumably assigned a long title for a reason, I would hate to shorten it before import just to make sure that it fits when re-used as a caption. Thanks, Brian > On May 24, 2018, at 5:25 PM, Timothy Dilauro wrote: > > Hi Brian, > > I don't think it's a good idea to change the data model just to avoid imports failing, though there may be other rationales that result in such a change. > > In the mean time, it might be useful to write some XSLT or some other custom code to perform sanity checks relative to ASpace restrictions ahead of EAD import attempts. In that manner, those non-conformant captions (and anything else you check on) could be tweaked before import. > > Cheers, > ~Tim > >> On May 23, 2018, at 2:39 PM, Brian Harrington wrote: >> >> >> Currently when importing an EAD, s are used to create digital objects. As part of this process, the @title attribute is used for both the digital object title, and the caption under file versions. I've recently run into a fun issue with s with @titles longer than 255 characters. These titles are OK for digital_object:title, which is VARCHAR(8704) but too long for file_version:caption, which is VARCHAR(255). So the import fails. >> >> Should this be considered a bug? If it is, and if one were theoretically considering a PR, would it make more sense to harmonize the length of the title and caption, or truncate the caption to 255 characters? My inclination is just to increase the maximum length of captions, and rely on people to show restraint, but I know that other people might have different opinions. >> >> Thanks, >> >> Brian >> >> -- >> Brian Harrington >> Migration Specialist >> LYRASIS >> brian.harrington at lyrasis.org >> skype: abbistani >> >> >> _______________________________________________ >> 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 From buschedw at msu.edu Fri May 25 14:08:23 2018 From: buschedw at msu.edu (Busch, Ed) Date: Fri, 25 May 2018 18:08:23 +0000 Subject: [Archivesspace_Users_Group] Adding events and undefined field names Message-ID: <35E2A8E8997F6C48A5D5FC21602BDEB60125DC875E@CAD-EX01.campusad.msu.edu> Hi- Which en.yml should be updated to add a new Event type? Is that the top one or the one under enums. I want to name some of the undefined fields in Accessions. I think I only see those in the top en.yml file, correct? The Users Manual documentation says it's the one in enums but I don't see them defined in it. Thanks! Ed Busch Electronic Records Archivist MSU Archives Conrad Hall, Room 101 888 Wilson Road East Lansing, MI 48824 517-884-6438 From dave_mayo at harvard.edu Fri May 25 20:55:04 2018 From: dave_mayo at harvard.edu (Mayo, Dave) Date: Sat, 26 May 2018 00:55:04 +0000 Subject: [Archivesspace_Users_Group] EAD Importer and DAOs In-Reply-To: <1EE5C4D0-ABF6-49D7-B456-4B81E5CF9044@lyrasis.org> References: <29DC4117-373A-43E3-B1CC-0EB465FD76AB@lyrasis.org> <38BE6D72-437B-464E-92BF-3D73E4F9D2A3@jhu.edu> <1EE5C4D0-ABF6-49D7-B456-4B81E5CF9044@lyrasis.org> Message-ID: IIRC, also, a lot of the smaller DB-level defaults (and some of the larger ones) are the result of various defaults or arbitrary guesses - before just saying that it's part of the data model and we should just live with it, one should always positively verify that it's legitimately part of the data model. In this case, I can actually negatively verify this: in the commit where the file_version:caption field is added, the DB migration doesn't specify a length (and so gets the default of 255), but the schema, which is specified, reads: > "caption" => {"type" => "string", "maxLength" => 16384}, So it's definitely a bug - I'll file a ticket, and I'm planning to make a pull request to fix this, though it won't really be a solution to your problem until it gets accepted and you update. If you have DB access, I think you'd be fine to just go directly in and run: ALTER TABLE `file_version` MODIFY caption VARCHAR(16384); Since you're expanding it, you won't risk truncating data. - Dave Mayo ASpace Core Committer's Group ?On 5/25/18, 9:34 AM, "archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Brian Harrington" wrote: Hi Tim, I agree it seems a bit backwards to change the data model to suit the importer, which is one of the reasons I decided to pose the question to the list. There could be valid reasons (display issues?) for limiting the length of the caption, but these things are often assigned somewhat arbitrarily, so I thought I would ask. If there are reasons for keeping for keeping the caption at 255, then I think it makes sense to truncate it in the importer, rather than just having things die on a database error. I currently use a modified version of Mark Custer?s schematron to check EADs prior to import, and can certainly add code to check @titles. The problem with doing that is the double use of @title for both digital_object:title and file_version:caption. Since ASpace supports long titles, and the archivist presumably assigned a long title for a reason, I would hate to shorten it before import just to make sure that it fits when re-used as a caption. Thanks, Brian > On May 24, 2018, at 5:25 PM, Timothy Dilauro wrote: > > Hi Brian, > > I don't think it's a good idea to change the data model just to avoid imports failing, though there may be other rationales that result in such a change. > > In the mean time, it might be useful to write some XSLT or some other custom code to perform sanity checks relative to ASpace restrictions ahead of EAD import attempts. In that manner, those non-conformant captions (and anything else you check on) could be tweaked before import. > > Cheers, > ~Tim > >> On May 23, 2018, at 2:39 PM, Brian Harrington wrote: >> >> >> Currently when importing an EAD, s are used to create digital objects. As part of this process, the @title attribute is used for both the digital object title, and the caption under file versions. I've recently run into a fun issue with s with @titles longer than 255 characters. These titles are OK for digital_object:title, which is VARCHAR(8704) but too long for file_version:caption, which is VARCHAR(255). So the import fails. >> >> Should this be considered a bug? If it is, and if one were theoretically considering a PR, would it make more sense to harmonize the length of the title and caption, or truncate the caption to 255 characters? My inclination is just to increase the maximum length of captions, and rely on people to show restraint, but I know that other people might have different opinions. >> >> Thanks, >> >> Brian >> >> -- >> Brian Harrington >> Migration Specialist >> LYRASIS >> brian.harrington at lyrasis.org >> skype: abbistani >> >> >> _______________________________________________ >> 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 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group From dave_mayo at harvard.edu Fri May 25 21:08:14 2018 From: dave_mayo at harvard.edu (Mayo, Dave) Date: Sat, 26 May 2018 01:08:14 +0000 Subject: [Archivesspace_Users_Group] EAD Importer and DAOs In-Reply-To: References: <29DC4117-373A-43E3-B1CC-0EB465FD76AB@lyrasis.org> <38BE6D72-437B-464E-92BF-3D73E4F9D2A3@jhu.edu> <1EE5C4D0-ABF6-49D7-B456-4B81E5CF9044@lyrasis.org> Message-ID: <98A9EFEE-5FE1-4627-AC76-7FE95DADF480@harvard.edu> Whoops, sorry - That's too big for varchar, you'd have to do: ALTER TABLE `file_version` MODIFY caption TEXT; - Dave ?On 5/25/18, 8:55 PM, "archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Mayo, Dave" wrote: IIRC, also, a lot of the smaller DB-level defaults (and some of the larger ones) are the result of various defaults or arbitrary guesses - before just saying that it's part of the data model and we should just live with it, one should always positively verify that it's legitimately part of the data model. In this case, I can actually negatively verify this: in the commit where the file_version:caption field is added, the DB migration doesn't specify a length (and so gets the default of 255), but the schema, which is specified, reads: > "caption" => {"type" => "string", "maxLength" => 16384}, So it's definitely a bug - I'll file a ticket, and I'm planning to make a pull request to fix this, though it won't really be a solution to your problem until it gets accepted and you update. If you have DB access, I think you'd be fine to just go directly in and run: ALTER TABLE `file_version` MODIFY caption VARCHAR(16384); Since you're expanding it, you won't risk truncating data. - Dave Mayo ASpace Core Committer's Group On 5/25/18, 9:34 AM, "archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Brian Harrington" wrote: Hi Tim, I agree it seems a bit backwards to change the data model to suit the importer, which is one of the reasons I decided to pose the question to the list. There could be valid reasons (display issues?) for limiting the length of the caption, but these things are often assigned somewhat arbitrarily, so I thought I would ask. If there are reasons for keeping for keeping the caption at 255, then I think it makes sense to truncate it in the importer, rather than just having things die on a database error. I currently use a modified version of Mark Custer?s schematron to check EADs prior to import, and can certainly add code to check @titles. The problem with doing that is the double use of @title for both digital_object:title and file_version:caption. Since ASpace supports long titles, and the archivist presumably assigned a long title for a reason, I would hate to shorten it before import just to make sure that it fits when re-used as a caption. Thanks, Brian > On May 24, 2018, at 5:25 PM, Timothy Dilauro wrote: > > Hi Brian, > > I don't think it's a good idea to change the data model just to avoid imports failing, though there may be other rationales that result in such a change. > > In the mean time, it might be useful to write some XSLT or some other custom code to perform sanity checks relative to ASpace restrictions ahead of EAD import attempts. In that manner, those non-conformant captions (and anything else you check on) could be tweaked before import. > > Cheers, > ~Tim > >> On May 23, 2018, at 2:39 PM, Brian Harrington wrote: >> >> >> Currently when importing an EAD, s are used to create digital objects. As part of this process, the @title attribute is used for both the digital object title, and the caption under file versions. I've recently run into a fun issue with s with @titles longer than 255 characters. These titles are OK for digital_object:title, which is VARCHAR(8704) but too long for file_version:caption, which is VARCHAR(255). So the import fails. >> >> Should this be considered a bug? If it is, and if one were theoretically considering a PR, would it make more sense to harmonize the length of the title and caption, or truncate the caption to 255 characters? My inclination is just to increase the maximum length of captions, and rely on people to show restraint, but I know that other people might have different opinions. >> >> Thanks, >> >> Brian >> >> -- >> Brian Harrington >> Migration Specialist >> LYRASIS >> brian.harrington at lyrasis.org >> skype: abbistani >> >> >> _______________________________________________ >> 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 _______________________________________________ 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 From mark.custer at yale.edu Fri May 25 08:48:00 2018 From: mark.custer at yale.edu (Custer, Mark) Date: Fri, 25 May 2018 12:48:00 +0000 Subject: [Archivesspace_Users_Group] EAD Importer and DAOs In-Reply-To: <38BE6D72-437B-464E-92BF-3D73E4F9D2A3@jhu.edu> References: <29DC4117-373A-43E3-B1CC-0EB465FD76AB@lyrasis.org> <38BE6D72-437B-464E-92BF-3D73E4F9D2A3@jhu.edu> Message-ID: Brian, Tim: In my opinion, the entire digital object module deserves a review, and that would include both EAD imports and exports (in those exports, for example, the digital object title is repeated as both an @xlink:title AND a daodesc/p; and worse yet, the ASpace required identifier isn't even included in the export). In general, I think that some of the import/export and migration tools in Aspace assume more than they should. In this case, I don't think that the importer should assume that it must repurpose a title as a caption, especially since the caption is not required by ASpace. So in the short term, if anything is done, I'd think that the importer should stop duplicating the title information in two places in the database. Any time data is duplicated like that (not to mention being repurposed for a completely different field), the odds for messy metadata goes way up. And there would be other ways to get around this in the meantime, such as shortening the DAO title and then updating it after the import... but even then, you'd have to ask: do we really want that title repeated in the caption field? Mark -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Timothy Dilauro Sent: Thursday, 24 May, 2018 5:26 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] EAD Importer and DAOs Hi Brian, I don't think it's a good idea to change the data model just to avoid imports failing, though there may be other rationales that result in such a change. In the mean time, it might be useful to write some XSLT or some other custom code to perform sanity checks relative to ASpace restrictions ahead of EAD import attempts. In that manner, those non-conformant captions (and anything else you check on) could be tweaked before import. Cheers, ~Tim > On May 23, 2018, at 2:39 PM, Brian Harrington wrote: > > > Currently when importing an EAD, s are used to create digital objects. As part of this process, the @title attribute is used for both the digital object title, and the caption under file versions. I've recently run into a fun issue with s with @titles longer than 255 characters. These titles are OK for digital_object:title, which is VARCHAR(8704) but too long for file_version:caption, which is VARCHAR(255). So the import fails. > > Should this be considered a bug? If it is, and if one were theoretically considering a PR, would it make more sense to harmonize the length of the title and caption, or truncate the caption to 255 characters? My inclination is just to increase the maximum length of captions, and rely on people to show restraint, but I know that other people might have different opinions. > > Thanks, > > Brian > > -- > Brian Harrington > Migration Specialist > LYRASIS > brian.harrington at lyrasis.org > skype: abbistani > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_grou > p > From mhughes at library.ucla.edu Tue May 29 12:47:14 2018 From: mhughes at library.ucla.edu (Hughes, Margaret) Date: Tue, 29 May 2018 16:47:14 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Integrations Wish List Message-ID: Hi all, The Integrations sub-team of TAC (Technical Advisory Council) is interested in hearing about your most desired ArchivesSpace integrations. What other systems and software do you wish ASpace could talk to? This could be anything - large or small, common or uncommon. Trello, your ILS, Slack, etc etc - whatever comes to mind! Send your replies on- or off-list. Any input is much appreciated! Thank you, Maggie, on behalf of the TAC Integrations sub-team ---------------------------------- Margaret Hughes Collections Data Archivist 310.206.6203 UCLA Library Special Collections A1713 Charles E. Young Research Library Los Angeles, CA 90095-1575 -------------- next part -------------- An HTML attachment was scrubbed... URL: From seth.shaw at unlv.edu Tue May 29 13:07:40 2018 From: seth.shaw at unlv.edu (Seth Shaw) Date: Tue, 29 May 2018 10:07:40 -0700 Subject: [Archivesspace_Users_Group] ArchivesSpace Integrations Wish List In-Reply-To: References: Message-ID: Something that came up in the recent community call is the ability to connect ArchivesSpace to digital asset management systems (e.g. CONTENTdm). For example, we use a script[1] to find all of the objects in CONTENTdm that match the title, date, and collection identifier fields to create ArchivesSpace digital objects + instances so that the AS EAD and PDF exports will link to our objects in CONTENTdm. Granted, this title/date matching wasn't perfect, but 97% was close enough that the remaining 14 could be easily reviewed manually. This sure beats making a few thousand, or even a few hundred manual digital object records. Of course, I'm running this script on my own computer which isn't an ideal workflow. It would be better if this were a plugin with a drop-down menu button and configuration screen so that ArchivesSpace users can initiate the matching and import on their own. If someone wants to port the code to Ruby, make the necessary configuration pages, and/or generally improve it; I think there are plenty of people who would appreciate it. 1: https://github.com/seth-shaw-unlv/small-stuff/blob/master/cdm-update-as/cdm_link_as.py On Tue, May 29, 2018 at 9:47 AM, Hughes, Margaret wrote: > Hi all, > > > > The Integrations sub-team of TAC (Technical Advisory Council) is > interested in hearing about your most desired ArchivesSpace integrations. > What other systems and software do you wish ASpace could talk to? This > could be anything ? large or small, common or uncommon. Trello, your ILS, > Slack, etc etc ? whatever comes to mind! > > > > Send your replies on- or off-list. Any input is much appreciated! > > > > Thank you, > > > > Maggie, on behalf of the TAC Integrations sub-team > > > > > > ---------------------------------- > > Margaret Hughes > > Collections Data Archivist > > 310.206.6203 > > > > UCLA Library Special Collections > > A1713 Charles E. Young Research Library > > Los Angeles, CA 90095-1575 > > > > _______________________________________________ > 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.Kim at lyrasis.org Tue May 29 14:32:53 2018 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Tue, 29 May 2018 18:32:53 +0000 Subject: [Archivesspace_Users_Group] Call for ArchivesSpace 4th Annual Member Forum speakers & topics (Aug 14, 2018) Message-ID: [cid:image003.jpg at 01D3F740.C6F551D0] Hello ArchivesSpace members, ArchivesSpace will be holding its fourth annual Member Forum on August 14, 2018 in Washington, DC. (Location TBA.) Just as in previous years, this will be a free opportunity for staff from ArchivesSpace member institutions to meet and share information with each other and the program team about all things ArchivesSpace. More information on the developing program is on the ArchivesSpace wiki at https://archivesspace.atlassian.net/wiki/display/ADC/ArchivesSpace+Member+Forum+2018. The planning group is looking for speakers to cover a range of topics. We've suggested a few themes on the form, but anything related to ArchivesSpace is fair game. We're looking for speakers for the proposed themes, with diverse experiences and perspectives represented throughout the day. We also welcome any suggestions for topics you'd like to learn or talk about at the meeting in morning plenary (full group) sessions, and afternoon workshops or small group sessions. Sessions may take any one of a number of formats, including panels, lightning rounds, and discussion groups. There is a short Google submission form available at https://goo.gl/forms/6L9UsylUz5u2Ws5n1; you can submit ideas or volunteer yourself to speak either via the form or by emailing me directly. Proposals, ideas, and suggestions received by June 26 will receive priority consideration so that we can get the program squared away as soon as possible. You will receive a response by July 13. If you have any questions or other suggestions at this point, please feel free to email Kim at christine.kim at lyrasis.org. Registration for the Member Forum will open later this spring. Thanks in advance for your help in making this a great event! Christine Kim ArchivesSpace Community Engagement Coordinator christine.kim at lyrasis.org 800.999.8558 x4820 404.592.4820 Skype: ckim.lyrasis -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 63280 bytes Desc: image003.jpg URL: From jteitelbaum at pabmc.net Wed May 30 15:42:13 2018 From: jteitelbaum at pabmc.net (Teitelbaum, Jesse) Date: Wed, 30 May 2018 15:42:13 -0400 Subject: [Archivesspace_Users_Group] Batch edits after migration Message-ID: We migrated finding aids from ARCHON to ArchivesSpace (2.1.1). All the Top Containers came over as Folders. I need to change the Top Containers to BOXES and then move the folders to the CHILD TYPE and CHILD INDICATOR. I started editing them one entry at a time, but some collections have many boxes and some boxes have many folders. Is there a way to edit in batches? Jesse Teitelbaum | Programs Coordinator Pennsylvania House of Representatives 133 Main Capitol Building | Harrisburg PA 17120 Phone: 717.787.4458 Email: jteitelbaum at pabmc.net www.pahousefellowship.us [cid:image001.jpg at 01D3F82C.C758A040] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 1067 bytes Desc: image001.jpg URL: From Kevin.Clair at du.edu Wed May 30 17:22:35 2018 From: Kevin.Clair at du.edu (Kevin Clair) Date: Wed, 30 May 2018 21:22:35 +0000 Subject: [Archivesspace_Users_Group] support for agent name forms in RTL scripts Message-ID: <5BBC1452-C495-4BE2-8EF9-DCDA789E98BF@du.edu> Hello, Has there been any consideration given to the possibility of encoding name forms for Agents in right-to-left scripts? This is something we would get some use out of at DU, since we have a number of Hebrew and Arabic personal names in our collections. I searched through the list archives and the current JIRA tickets but couldn?t find anything along these lines. Not a high-priority request for us, I was just curious if anyone else had requested it. thanks! -k -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Thu May 31 09:00:29 2018 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Thu, 31 May 2018 13:00:29 +0000 Subject: [Archivesspace_Users_Group] policy change for ArchivesSpace membership level criteria for non-academic and freestanding archives Message-ID: Dear ArchivesSpace members, ArchivesSpace is celebrating its five-year anniversary as a membership program this year. We're very appreciative of the support we've received from our members and the larger archival community in that time. We think it's a good time to reflect and to review a few of our policies and activities, with the goal of better serving our community, including some parts that we believe may have been underserved in the past. I'm writing to you today about a change in our membership level criteria for free-standing and non-academic archives that was recently approved by the ArchivesSpace Governance Board. Beginning with the 2018/2019 membership term, which starts July 1, the membership level criteria for these types of archives will be as follows: Free-Standing or Non-Academic Archives: JSTOR or Artstor Classification Total FTE Staff (only for those without a JSTOR or Artstor Classification) ArchivesSpace Level Annual Fee Very Large 401+ Very Large $7500 Large 301-400 Large $5000 Medium 151-300 Medium $3000 Small 51-150 Small $1000 Very Small 0-50 Very Small $300 This represents higher FTE thresholds across the board for non-academic institutions, which may mean that some institutions that were previously classified at a higher level will now be classified at a lower level (for example, a non-academic institution with 30 FTE would have been Small under the previous criteria; it will now be Very Small). No institutions will have their level raised, but some may be lowered. This change does not affect current members that are academic institutions, anyone already using a JSTOR or Artstor classification, or those already at the Very Small level. Our membership benefits continue to be the same at every level. We have contacted the small number of institutions in our current membership that we believe may be positively affected by this change. If we haven't contacted you and you believe you may be eligible for a reclassification, please email me. We still consider JSTOR and Artstor classifications to be the best and fairest measures for membership level, because they take a nuanced view of institutional capacity, and we will continue to request JSTOR or Artstor classifications from all institutions for whom they are appropriate during the membership application process. ArchivesSpace membership provides for the long-term development and sustainability of the application, and our intent is to give institutions of all sizes and types the ability to contribute toward its future and participate in our community. We aim to be equitable and fair in applying our membership levels, and believe that changing this specific policy will enable better parity with our classification criteria for academic institutions and others in our community who have JSTOR or Artstor classifications. We very much hope it will encourage certain types of institutions that found it difficult to participate under the previous classification system to join us. Thank you for your continued support and all you have done to build our community in its first five years. We look forward to continuing to grow and mature even more in the next five. All best, 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: image002.jpg Type: image/jpeg Size: 6608 bytes Desc: image002.jpg URL: From WangCH at si.edu Thu May 31 12:22:46 2018 From: WangCH at si.edu (Wang, Ching-Hsien) Date: Thu, 31 May 2018 16:22:46 +0000 Subject: [Archivesspace_Users_Group] policy change for ArchivesSpace membership level criteria for non-academic and freestanding archives In-Reply-To: References: Message-ID: Christine We are happy to continue our payment. Could you please send me an invoice? I will get the purchase order process start. Thank you. Ching-hsien Library and Archives System Support Branch, Collections Systems & Digital Assets Division, OCIO Capital Gallery, 600 Maryland Ave. SW, Suite 4000, MRC 503 Washington DC. 20024 Phone: 202-633-5581 Documentations: Transcription Center , ASpace, LASSB documentations. From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Christine Di Bella Sent: Thursday, May 31, 2018 9:00 AM To: Archivesspace Users Group ; Archivesspace Member Reps Cc: ArchivesSpace Board of Trustees mail list Subject: [Archivesspace_Users_Group] policy change for ArchivesSpace membership level criteria for non-academic and freestanding archives Dear ArchivesSpace members, ArchivesSpace is celebrating its five-year anniversary as a membership program this year. We're very appreciative of the support we've received from our members and the larger archival community in that time. We think it's a good time to reflect and to review a few of our policies and activities, with the goal of better serving our community, including some parts that we believe may have been underserved in the past. I'm writing to you today about a change in our membership level criteria for free-standing and non-academic archives that was recently approved by the ArchivesSpace Governance Board. Beginning with the 2018/2019 membership term, which starts July 1, the membership level criteria for these types of archives will be as follows: Free-Standing or Non-Academic Archives: JSTOR or Artstor Classification Total FTE Staff (only for those without a JSTOR or Artstor Classification) ArchivesSpace Level Annual Fee Very Large 401+ Very Large $7500 Large 301-400 Large $5000 Medium 151-300 Medium $3000 Small 51-150 Small $1000 Very Small 0-50 Very Small $300 This represents higher FTE thresholds across the board for non-academic institutions, which may mean that some institutions that were previously classified at a higher level will now be classified at a lower level (for example, a non-academic institution with 30 FTE would have been Small under the previous criteria; it will now be Very Small). No institutions will have their level raised, but some may be lowered. This change does not affect current members that are academic institutions, anyone already using a JSTOR or Artstor classification, or those already at the Very Small level. Our membership benefits continue to be the same at every level. We have contacted the small number of institutions in our current membership that we believe may be positively affected by this change. If we haven't contacted you and you believe you may be eligible for a reclassification, please email me. We still consider JSTOR and Artstor classifications to be the best and fairest measures for membership level, because they take a nuanced view of institutional capacity, and we will continue to request JSTOR or Artstor classifications from all institutions for whom they are appropriate during the membership application process. ArchivesSpace membership provides for the long-term development and sustainability of the application, and our intent is to give institutions of all sizes and types the ability to contribute toward its future and participate in our community. We aim to be equitable and fair in applying our membership levels, and believe that changing this specific policy will enable better parity with our classification criteria for academic institutions and others in our community who have JSTOR or Artstor classifications. We very much hope it will encourage certain types of institutions that found it difficult to participate under the previous classification system to join us. Thank you for your continued support and all you have done to build our community in its first five years. We look forward to continuing to grow and mature even more in the next five. All best, 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: 4074 bytes Desc: image001.jpg URL: From Christine.Kim at lyrasis.org Thu May 31 14:55:22 2018 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Thu, 31 May 2018 18:55:22 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Member Forum 2018 - Update on site! Message-ID: [cid:image001.jpg at 01D3F8D6.40906110] Hello ArchivesSpace members, Thank you for patiently holding on by the edges of your seats as we finalized the site for our fourth annual Member Forum! Please join us on August 14, 2018 at the Josephine Butler Parks Center in Washington, DC. Washington Parks & People is the capital's hub for activating public lands & waters for broad community revitalization, with a mission to grow city-wide park-based community health & vitality by nurturing innovation & partnerships. We are thrilled to have our annual forum held at this location. The Josephine Butler Parks Center is just a quick subway ride away from the SAA conference hotel. We will share parking and transportation information shortly. In the meantime, the planning group continues to look for speakers, workshop instructors, discussion leaders, panelists, and topic suggestions. There is a short Google submission form available at https://goo.gl/forms/6L9UsylUz5u2Ws5n1; you can submit ideas or volunteer yourself to speak either via the form or by emailing me directly. Proposals, ideas, and suggestions received by June 26 will receive priority consideration so that we can get the program squared away as soon as possible. You will receive a response by July 13. More information on the developing program is on the ArchivesSpace wiki at https://archivesspace.atlassian.net/wiki/display/ADC/ArchivesSpace+Member+Forum+2018. Registration for the event will open early July. If you have any questions or other suggestions at this point, please feel free to email Kim at christine.kim at lyrasis.org. Thanks in advance for your help in making this a great event! Christine Kim ArchivesSpace Community Engagement Coordinator christine.kim at lyrasis.org 800.999.8558 x4820 404.592.4820 Skype: ckim.lyrasis -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 63145 bytes Desc: image001.jpg URL: From christine.dibella at lyrasis.org Thu May 31 18:02:14 2018 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Thu, 31 May 2018 22:02:14 +0000 Subject: [Archivesspace_Users_Group] release candidate available - ArchivesSpace v2.4.0-RC1 Message-ID: The ArchivesSpace team is pleased to announce a release candidate, v2.4.0-RC1. You can download it at https://github.com/archivesspace/archivesspace/releases/tag/v2.4.0-RC1 or test it out without downloading at http://test.archivesspace.org/staff (username admin /password admin). This release candidate contains many program-led and community pull requests that provide feature enhancements, bug fixes, infrastructure improvements, and documentation updates. Some items of note include improvements to the search results screen in the staff interface (including new columns for identifier and result context for archival objects), updates to the mapping and new options for our built-in MARCXML exporter for resources, a new option to search subjects in the PUI, and updates to the French translations. There are also fixes to some bugs with permissions, the OAI-PMH responder, an erroneous error message in the PUI when using the back button with some browsers, and orphaned instance records being created when digital objects were deleted. Thanks to the many community members who made contributions to this release, including both individual developers and our Development Prioritization sub-team, Testing sub-team, and Core Committers Group. The release notes give you a sense of just how many people are working alongside the program team to help make ArchivesSpace better. We so appreciate all of you. Please try this release candidate out and let us know by June 6 at ArchivesSpaceHome at lyrasis.org if you notice any problems with the specific areas that are addressed in this release, or if anything that was working before no longer is. Barring major issues, we expect to release 2.4.0 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: image002.jpg Type: image/jpeg Size: 6608 bytes Desc: image002.jpg URL: From Christine.Kim at lyrasis.org Thu May 31 18:34:49 2018 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Thu, 31 May 2018 22:34:49 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Update - May 2018 Message-ID: [ASpaceOrgHome.jpg] May 2018 Update We are excited to share exciting community updates, including updates on regional forums and the upcoming 4th annual Member Forum. New stories are up on the blog, and we have another great webinar coming up in June! Read on for more news! Development The ArchivesSpace team is pleased to announce a release candidate for our next version. It is available at https://github.com/archivesspace/archivesspace/releases/tag/v2.4.0-RC1. This release candidate includes improvements to the search results screen in the staff interface (including new columns for the identifier and the result context), updates to the mapping and a new option for our built-in MARCXML exporter for resources, a new option to search subjects in the PUI, and updates to the French translations. There are also fixes to some bugs with permissions, the OAI-PMH responder, an erroneous error message in the PUI when using the back button with some browsers, and orphaned instance records being created when digital objects were deleted. Please try this release candidate out and let us know by June 6 at ArchivesSpaceHome at lyrasis.org if you notice any problems with the specific areas that are addressed in this release, or if anything that was working before no longer is. Barring major issues, we expect to release 2.4.0 next week. We expect to put out a PUI search improvement-specific release later in June pending further internal testing. Annual Member Forum: August 14, 2018, in Washington D.C. ArchivesSpace will be holding its fourth annual Member Forum on August 14, 2018 at the Josephine Butler Parks Center in Washington, DC. Washington Parks & People is the capital's hub for activating public lands & waters for broad community revitalization, with a mission to grow city-wide park-based community health & vitality by nurturing innovation & partnerships. We are thrilled to have our annual forum held at this location. Just as in previous years, this will be a free opportunity for staff from ArchivesSpace member institutions to meet and share information with each other and the program team about all things ArchivesSpace. More information on the developing program is on the ArchivesSpace wiki at https://archivesspace.atlassian.net/wiki/display/ADC/ArchivesSpace+Member+Forum+2018. The planning group is looking for speakers to cover a range of topics. There is a short Google submission form available at https://goo.gl/forms/6L9UsylUz5u2Ws5n1; you can submit ideas or volunteer yourself to speak. Proposals, ideas, and suggestions received by June 26 will receive priority consideration so that we can get the program squared away as soon as possible. You will receive a response by July 13. If you have any questions or other suggestions at this point, please feel free to email Kim at christine.kim at lyrasis.org. Registration for the Member Forum will open early July. Thanks in advance for your help in making this a great event! Webinar: Transforming XSL to EAD: Importing Component Hierarchies: May 27 at 1-2:30pm ET (10-11:30am PT) Do you list out your components on a spreadsheet before committing the item records into ArchivesSpace? If this is your preferred processing workflow, you're not alone. In this webinar, we will look at three distinct methods to get your spreadsheet lists into your ArchivesSpace resource record to populate components. Elizabeth Perkes (Utah State Archives) will demonstrate a workflow that uses built-in Microsoft Office tools to convert Microsoft Excel spreadsheets to EAD via mail merge. Jason Ronallo (North Carolina State University) will provide a demo of the STEAD schema and STEADY tool. And Ben Johnson (Harvard Business School) uses a spreadsheet importer plugin developed by Bobbi Fox (Harvard University) in a variety of ways. However, he will provide an overview of one simple use of the tool: How to easily and quickly add bulk data from new accessions to existing resources. Ben will walk through our workflow for that and show some limitations and pitfalls to avoid. But perhaps you would like to see more than just workflows. Kelly Spring (East Carolina University) will provide insight into some of the common troubleshooting and other tasks that will help you successfully upload the EAD to ArchivesSpace. Please join us on May 27, 2018 at 1-2:30pm ET (10-11:30am PT) as Elizabeth, Jason, Ben, and Kelly share a variety of practices to import your spreadsheet contents into ArchivesSpace. Please feel free to bring any questions you have. The webinar will be available through: http://lyrasis.adobeconnect.com/ruio9pyqjot4/ and the recording will be available at a later date on the ArchivesSpace YouTube channel: https://www.youtube.com/channel/UCxR6D-UlSx6N6UWTeqHTjzA. No registration required. The session is limited to the first 100 participants. Please feel free to host a webinar viewing group. If you have any questions about this webinar, please contact Kim at christine.kim at lyrasis.org. We look forward to seeing you at the webinar! Regional Forum Updates ArchivesSpace regional forums are opportunities for our diverse ArchivesSpace members to meet up more locally to share and learn from each other through program content shaped by the community. Upcoming: SoCal Regional Forum: June 28, 2018 at University of California, Irvine * Registration is open until June 27th. But register by June 5th to cast your vote for the afternoon activity: https://www.eventbrite.com/e/archivesspace-regional-forum-southern-california-2018-tickets-44930947674 * Call for lightning round speakers: The SoCal Regional Forum Working Group is seeking proposals for a lightning round session. Presentations will be capped at 5 minutes and topics can be on anything related to your work using, developing, implementing, or actively contributing to the ArchivesSpace application and community. Submit a short proposal at https://goo.gl/forms/zowXsJvLWBPa0Bts1 by Thursday, May 31, 2018. * The program is taking shape! Keep up to date: https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/533168147/SoCal+Regional+Forum Past: Boston Regional Forum: May 3, 2018 at Tufts University Thanks to all who attended and made the Boston Regional Forum such a lively event! Do you have photos to share? Please feel free to add them to this google drive folder: https://goo.gl/LKUeWv * Notes: Links to the notes are up on the wiki. Do you have notes you'd like to share? Please add them to this google drive folder: https://goo.gl/yHq7dQ * Slides: All presentation slides are also up on the wiki, including slides from the plug-ins overview workshop: https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/455213059/Boston+Regional+Forum+-+May+2018 If you have any questions or ideas about regional forums, feel free to email Kim at christine.kim at lyrasis.org. New Stories on the Blog In All About Community (http://archivesspace.org/category/all-about-community/), Scott Hanrath (Assistant Dean for Digital Initiatives and Discovery Services, University of Kansas Libraries) provides insight into the Technical Documentation sub-team. This is a continuation of a series looking into the various sub-teams of the Technical Advisory Council and User Advisory Council to provide insight into the variety of activities and initiatives undertaken by these groups. In User Insights (http://archivesspace.org/category/user-insights/), Adrienne Harling (Archivist, San Francisco Symphony) shares on her experience successfully organizing an ArchivesSpace workshop for smaller institutions in her region. We would love to include your ArchivesSpace stories on the blog! If you would like to contribute, please email Kim at christine.kim at lyrasis.org. Change in Membership Level Criteria for Free-Standing and Non-Academic Archives The ArchivesSpace Governance Board recently approved a change in our membership level criteria for free-standing and non-academic archives. Beginning with the 2018/2019 membership term, which starts July 1, the membership level criteria for these types of archives will be as follows: Free-Standing or Non-Academic Archives: JSTOR or Artstor Classification Total FTE Staff (only for those without a JSTOR or Artstor Classification) ArchivesSpace Level Annual Fee Very Large 401+ Very Large $7500 Large 301-400 Large $5000 Medium 151-300 Medium $3000 Small 51-150 Small $1000 Very Small 0-50 Very Small $300 This represents higher FTE thresholds across the board for free-standing and non-academic institutions, which may mean that some institutions that were previously classified at a higher level will now be classified at a lower level. This change does not affect academic institutions, anyone with a JSTOR or Artstor classification, or those that were already classified at the Very Small level. Our membership benefits continue to be the same at every level. ArchivesSpace membership provides for the long-term development and sustainability of the application, and our intent is to give institutions of all sizes and types the ability to contribute toward its future and participate in our community. We very much hope this policy change will encourage certain types of institutions that found it difficult to participate under the previous classification system for free-standing and non-academic archives to join us. Membership Update We are excited to welcome our newest members to our community! Our new members since April 30 include: * California State University, Sacramento * Indiana University of Pennsylvania * Newman University (Wichita, Kansas) * Saint Mary's College of California (Moraga, California) As of May 31, we have 362 General members, 19 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 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 Section 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: image003.jpg Type: image/jpeg Size: 20006 bytes Desc: image003.jpg URL: