Re: [Archivesspace_Users_Group] Auto generating unique IDs
; +1 5149397001x1368 > cca.qc.ca > <https://can01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.cca.qc.ca%2Ffr%2F%3Futm_source%3Dfr_email_signature%26utm_medium%3Demail&data=05%7C01%7Cahaywood%40cca.qc.ca%7C0b0f136b66884b301a7208dad2528c3b%7C4e72076180cf4800ad14ca034727386b%7C0%7C0%7C638053549229451151%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=DgH7zITA9oXmNITIURPaCPq2qR86lSjmeD7gUyfnOqA%3D&reserved=0> > Twitter > <https://can01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.twitter.com%2Fccawire&data=05%7C01%7Cahaywood%40cca.qc.ca%7C0b0f136b66884b301a7208dad2528c3b%7C4e72076180cf4800ad14ca034727386b%7C0%7C0%7C638053549229451151%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=46AhPQ%2BvkSw5XXTnv5wLBcoFObm%2FsDYwpQ2LTHK4J%2FY%3D&reserved=0> > | Instagram > <https://can01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.instagram.com%2Fcanadiancentreforarchitecture%2F&data=05%7C01%7Cahaywood%40cca.qc.ca%7C0b0f136b66884b301a7208dad2528c3b%7C4e72076180cf4800ad14ca034727386b%7C0%7C0%7C638053549229607376%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=82bxWXhLmMA%2FwDLx%2FMNdj2%2Bi8NVcx6UygxtbZFE%2F0Y0%3D&reserved=0> > | Facebook > <https://can01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.facebook.com%2Fcca.conversation&data=05%7C01%7Cahaywood%40cca.qc.ca%7C0b0f136b66884b301a7208dad2528c3b%7C4e72076180cf4800ad14ca034727386b%7C0%7C0%7C638053549229607376%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=wruiAySg2Szie9R1oPZ6qpeXFipImm6e5D1UkG7k%2FjY%3D&reserved=0> > | YouTube > <https://can01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.youtube.com%2Fuser%2FCCAchannel&data=05%7C01%7Cahaywood%40cca.qc.ca%7C0b0f136b66884b301a7208dad2528c3b%7C4e72076180cf4800ad14ca034727386b%7C0%7C0%7C638053549229607376%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=jGI36qA5jItJ68YAMySBl73RNh4h81M6%2F2ziDfFAhIU%3D&reserved=0> > > Comment la technologie transforme-t-elle le paysage du commerce de détail? > <https://can01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbit.ly%2F3LQKFyg&data=05%7C01%7Cahaywood%40cca.qc.ca%7C0b0f136b66884b301a7208dad2528c3b%7C4e72076180cf4800ad14ca034727386b%7C0%7C0%7C638053549229607376%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=OPUAD%2FX4JjcwHsh4aqJdMhXp9TsxjbbZ%2BUOMbvK4IDo%3D&reserved=0> > How does technology transform retail landscapes? > <https://can01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbit.ly%2F3BQMt60&data=05%7C01%7Cahaywood%40cca.qc.ca%7C0b0f136b66884b301a7208dad2528c3b%7C4e72076180cf4800ad14ca034727386b%7C0%7C0%7C638053549229607376%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=WMPewIZj324s%2FVnWwOUfptSnIL%2BLd8bbdI5GHVeLHHk%3D&reserved=0> > > Inscrivez-vous > <https://can01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.cca.qc.ca%2Ffr%2F%3Fgo%3Denews%26utm_source%3Dfr_email_signature%26utm_medium%3Demail&data=05%7C01%7Cahaywood%40cca.qc.ca%7C0b0f136b66884b301a7208dad2528c3b%7C4e72076180cf4800ad14ca034727386b%7C0%7C0%7C638053549229607376%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=UoI4QitBCIdg4z%2FfAh48%2BIIeDkDFTw%2FG7Ly0%2BHmT2nQ%3D&reserved=0> > pour recevoir de nos nouvelles. > Sign up > <https://can01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.cca.qc.ca%2Fen%2F%3Fgo%3Denews%26utm_source%3Den_email_signature%26utm_medium%3Demail&data=05%7C01%7Cahaywood%40cca.qc.ca%7C0b0f136b66884b301a7208dad2528c3b%7C4e72076180cf4800ad14ca034727386b%7C0%7C0%7C638053549229607376%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=l6jw8uMZvKArSWz%2Fyy%2F2SLOHZN3rPJPxW%2FKk7XZOSSc%3D&reserved=0> > to get news from us. > > *From:* archivesspace_users_group-boun...@lyralists.lyrasis.org < > archivesspace_users_group-boun...@lyralists.lyrasis.org> *On Behalf Of > *Alexander > Duryee > *Sent:* Tuesday, November 29, 2022 3:13 PM > *To:* Archivesspace Users Group < > archivesspace_users_group@lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] Auto generating unique IDs > > > > Anna, > > > > We use a plugin to achieve something very similar here at NYPL - > https://github.com/alexduryee/aspace_serial_numbers > <
Re: [Archivesspace_Users_Group] Auto generating unique IDs
=AkDvIr0ydespIHaIcj49qiDGZaTZBZ2ACpZbJtFjC_JDtQj9dDaUitg4BlxqfBIE&s=Qc6RdWh-Qnne4nIG0e03fJ9leMf8ZlRyTstlTrW19xE&e=> >> >> Inscrivez-vous >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.cca.qc.ca_fr_-3Fgo-3Denews-26utm-5Fsource-3Dfr-5Femail-5Fsignature-26utm-5Fmedium-3Demail&d=DwMFAg&c=slrrB7dE8n7gBJbeO0g-IQ&r=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=AkDvIr0ydespIHaIcj49qiDGZaTZBZ2ACpZbJtFjC_JDtQj9dDaUitg4BlxqfBIE&s=yAd5JxLFVGSNRWh5EomGXvTsdobHVbxOPA-GaTRxFaY&e=> >> pour recevoir de nos nouvelles. >> Sign up >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.cca.qc.ca_en_-3Fgo-3Denews-26utm-5Fsource-3Den-5Femail-5Fsignature-26utm-5Fmedium-3Demail&d=DwMFAg&c=slrrB7dE8n7gBJbeO0g-IQ&r=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=AkDvIr0ydespIHaIcj49qiDGZaTZBZ2ACpZbJtFjC_JDtQj9dDaUitg4BlxqfBIE&s=CYn7ydtYTY5_r_Oo8B0YldcaW4NWd01gasUV0ETmW6k&e=> >> to get news from us. >> ___ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group@lyralists.lyrasis.org >> >> https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwICAg&c=slrrB7dE8n7gBJbeO0g-IQ&r=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=AkDvIr0ydespIHaIcj49qiDGZaTZBZ2ACpZbJtFjC_JDtQj9dDaUitg4BlxqfBIE&s=vmmXCwYx00vAfjuB-kztT-F8avjxog1K1LpjYWk_mSM&e= >> > > > -- > Rachel Searcy > Accessioning Archivist, Archival Collections Management > New York University Libraries > 212.998.2539 | rachel.sea...@nyu.edu > My pronouns are she/her/hers > ___ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group@lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Alexander Duryee Manager, Archival Metadata New York Public Library (917)-229-9590 alexanderdur...@nypl.org ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
[Archivesspace_Users_Group] Archival Object Edits Not Always Saving
A user in our department has occasionally run into an issue where archival object record edits won't save after clicking Save Archival Object. This issue is not reliably repeatable, but is not infrequent either. I've watched them reproduce the error (open an AO, make an edit to a note, click Save Archival Object on the left sidebar, the old data appears on the new page), and there doesn't appear to be anything unusual in the process. When I checked the logs, the unedited record seems to be POSTed back, as if they did not change the record at all. I didn't see any errors, or anything amiss in general, around the POST. Is there anything that could be causing this? As far as I'm aware, it only impacts one user, although it's possible that others have the same issue but haven't said anything. Thanks, --Alex -- Alexander Duryee Manager, Archival Metadata New York Public Library (917)-229-9590 alexanderdur...@nypl.org ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
[Archivesspace_Users_Group] Timewalk for ArchivesSpace 3.0
All, The timewalk plugin for automated date parsing has been updated to support ArchivesSpace 3.0 and above. The new plugin is available at https://github.com/alexduryee/timewalk. The new version of timewalk is incompatible with ArchivesSpace 2.8 and below. If you need to install timewalk on an older version of ArchivesSpace, a compatible version is available here: https://github.com/alexduryee/timewalk/releases/tag/v2.x Please let me know if you run into any issues or have any questions. Thanks, --Alex -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderdur...@nypl.org ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
Re: [Archivesspace_Users_Group] Date Expression Parsing / Issues with Timewalk Plugin
Laurie, Thank you for bringing this to my attention - I've identified the problem (relationship definitions that may not still exist in 3.0.2) and will work on getting a fixed version of the plugin up ASAP. Thanks again, --Alex On Mon, Oct 4, 2021 at 12:43 PM Valerie Addonizio wrote: > Hi Laurie, > > > > I wanted to clarify one point you raised in your email. There is no > automatic date parsing in AS out of the box; I’m thinking that any date > parsing that you enjoyed was coming from Timewalk. The recent release notes > for AS 3.0.2 did talk about date parsing, but that was very specific to > preexisting dates in Agent records and was a one-time process associated > with the update past 3.0.0, at which point AS parses dates for Agents. That > date parsing isn’t referring to a feature in AS, just a one time script > that gets run as part of the update past 3.0.0 and then never again. > > > > This doesn’t help you, I know! I’m only clarifying that note associated > with 3.0.2 and beyond and that date parsing isn’t a feature (so I wouldn’t > expect a fix except from an updated timewalk plugin) > > > > -Valerie > > > > *From:* archivesspace_users_group-boun...@lyralists.lyrasis.org < > archivesspace_users_group-boun...@lyralists.lyrasis.org> *On Behalf Of *Benn > Joseph > *Sent:* Monday, October 4, 2021 12:30 PM > *To:* Archivesspace Users Group < > archivesspace_users_group@lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] Date Expression Parsing / > Issues with Timewalk Plugin > > > > This could be a good opportunity to plug this feature request: > > https://archivesspace.atlassian.net/browse/ANW-1273 > > > > Part of the reason we at one point considered using date expressions in > addition to normalized dates is because the normalized dates in the PUI are: > >- Not easily human-readable (i.e. “1935-03-19 - 1935-03-23”) >- Only partially compliant with DACS 2.4.14 (the example given in DACS >is “1906 March 17”; also, “Expression of dates as all numerals is >discouraged due to the differing conventions in the order of information” > > > > --Benn > > > > *From:* archivesspace_users_group-boun...@lyralists.lyrasis.org < > archivesspace_users_group-boun...@lyralists.lyrasis.org> *On Behalf Of *Dan > Michelson > *Sent:* Monday, October 04, 2021 9:38 AM > *To:* Archivesspace Users Group < > archivesspace_users_group@lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] Date Expression Parsing / > Issues with Timewalk Plugin > > > > Hi Laurie, > > > > I've never used the Timewalk plugin, but why use the date expression field > at all when you don't have to? That would avoid having to enter the same > information twice, aside from cases like "Spring 2020," which don't > translate perfectly to the normalized date fields. > > > > All the best, > > > > Dan > > > > On Mon, Oct 4, 2021 at 9:29 AM Laurie Sather wrote: > > Hi, > > > > Anyone else having trouble with the Date Expression no longer parsing out? > How is everyone else dealing with this? The timewalk plugin is no longer > compatible, so we had to disable it, which is very inconvenient to now have > to manually reenter all the same information. > > > > It sounded like Aspace was going to include a fix with v3.0.2, but the > automatic date expression parsing still does not function (with or without > the plugin). > > > > Solutions? > > > > Thank you! > > Laurie > > > > > > Laurie Sather, MA, MLIS, CA > > Head Archivist > > Archival Collections Department > > Hagley Museum and Library > > PO Box 3630 > > Wilmington, DE 19807-0630 > > Telephone: 302-658-2400 ext. 277 > > Email: lsat...@hagley.org > > > > ___ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group@lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > <https://urldefense.com/v3/__http:/lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group__;!!Dq0X2DkFhyF93HkjWTBQKhk!EbTwMfxfgl0_tDr-eM6uWB3x2Bp8T1BkloL3bhagVkPZNwJlVCqQZROf-gTTYoSEfYNckRVW$> > > > > -- > > Dan Michelson > > Project Manager Archivist > > Smith College Special Collections > > > > For current library access and services details, see Library Services > During COVID-19 > <https://urldefense.com/v3/__https:/libraries.smith.edu/library-services-during-covid-19__;!!Dq0X2DkFhyF93HkjWTBQKhk!EbTwMfxfgl0_tDr-eM6uWB3x2Bp8T1BkloL3bhagVkPZNwJlVCq
Re: [Archivesspace_Users_Group] normalized begin/end date display in PUI
felinks.protection.outlook.com/?url=http*3A*2F*2Flyralists.lyrasis.org*2Fmailman*2Flistinfo*2Farchivesspace_users_group&data=04*7C01*7Ckmc35*40psu.edu*7Cb55e1f010f9447f0577b08d8ff4dcec6*7C7cf48d453ddb4389a9c1c115526eb52e*7C0*7C0*7C637540056959026855*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C1000&sdata=c6lYvrhlXffiD37JlteoS9TW0Ix2PJVg5J1PxP7m4YQ*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJQ!!Dq0X2DkFhyF93HkjWTBQKhk!Fkq1I6E7XyinQKdUlen_4U4aO06pHrKfTJlMjvezF7IEWVXc05m_BOif_eFzWKKLXscSzYRR$> > > > > -- > > Dan Michelson > > Project Manager Archivist > > Smith College Special Collections > > > > Due to COVID-19, Special Collections is offering limited, remote reference > and digitization services and ongoing consultations for faculty, students, > and other researchers. Smith course support is our primary responsibility > at this time. All other requests and inquiries will be responded to as we > are able. > > > For information about Smith College’s response to Covid-19, please visit > the Smith College Libraries > <https://urldefense.com/v3/__https:/nam10.safelinks.protection.outlook.com/?url=http*3A*2F*2Fbit.ly*2FSCLcovid-19&data=04*7C01*7Ckmc35*40psu.edu*7Cb55e1f010f9447f0577b08d8ff4dcec6*7C7cf48d453ddb4389a9c1c115526eb52e*7C0*7C0*7C637540056959036854*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C1000&sdata=kXOc2OY9A56mfl7YfXO0JVFSEy3I7c9Sb1TXgroKYPs*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSU!!Dq0X2DkFhyF93HkjWTBQKhk!Fkq1I6E7XyinQKdUlen_4U4aO06pHrKfTJlMjvezF7IEWVXc05m_BOif_eFzWKKLXsXnOUo7$> > and Smith College > <https://urldefense.com/v3/__https:/nam10.safelinks.protection.outlook.com/?url=https*3A*2F*2Fwww.smith.edu*2Fstudent-life*2Fhealth-wellness*2Fcoronavirus&data=04*7C01*7Ckmc35*40psu.edu*7Cb55e1f010f9447f0577b08d8ff4dcec6*7C7cf48d453ddb4389a9c1c115526eb52e*7C0*7C0*7C637540056959036854*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C1000&sdata=WQ6qZVQLh7oyqAgwAmK4djVg24bNxKdhTroFR*2BNwwCs*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJSU!!Dq0X2DkFhyF93HkjWTBQKhk!Fkq1I6E7XyinQKdUlen_4U4aO06pHrKfTJlMjvezF7IEWVXc05m_BOif_eFzWKKLXhgt2EWm$> > websites. For information about library services during this time, > information is available on our website. > ___ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group@lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderdur...@nypl.org ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
Re: [Archivesspace_Users_Group] Changing Main PUI Search from OR to AND
Bailey,
Starting in ArchivesSpace 2.8.0, you can pass Solr parameters to the PUI
via config/config.rb. The default behavior in a fresh installation is
mm='100%', which I believe is (mostly) equivalent to using AND as the
default operator. I tested this on test.archivesspace.org (3.0.0-RC2), and
it appears to be using AND as its default - for example, searching
"benjamin stockton" (without quotes) returns "Benjamin and Julia Stockton
Rush papers" but not "Benjamin Harrison papers".
If you're using 2.8.0 or newer, I would check the config/config.rb to see
if the following line is present and not commented out:
AppConfig[:solr_params] = { 'mm' => '100%' }
For older versions, you'll need to write a plug-in to override the default
Solr parameters generated by the PUI.
Thanks,
--Alex
On Thu, Apr 22, 2021 at 10:52 AM Hoffner, Bailey E. wrote:
> Morning All,
>
>
>
> I know I’ve seen conversations about this before, but because I can’t
> think of the appropriate technical terminology, I haven’t been able to
> easily locate those convos in the listserv archive.
>
>
>
> We are interested in changing the automatic search function on the PUI
> from using “or” between search terms, to using “and.” Any help appreciated
> (including just pointing me to previous convos I wasn’t able to locate 😊
> ).
>
>
>
> -Bailey
>
>
>
> Bailey Hoffner, MLIS
>
> Pronouns: she/her/hers
>
> Metadata and Collections Management Archivist
>
> University of Oklahoma Libraries
>
> bail...@ou.edu
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
--
Alexander Duryee
Metadata Archivist
New York Public Library
(917)-229-9590
alexanderdur...@nypl.org
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
Re: [Archivesspace_Users_Group] Automated Tests for Plugins?
Christina, I'm unaware of any way to implement plugin tests into ASpace's existing test infrastructure. What we did was write RSpec tests outside of the ASpace release, which start the application (with our plugins), populate it with data via the API, and check the outputs of common tasks against fixtures. There's probably a better way of doing this (e.g. packaging the tests in the plugin directory, and having RSpec pull them out, instead of having them all in a big spec directory), but so far this has worked for us. Thanks, --Alex On Tue, Feb 25, 2020 at 1:56 PM Cortland, Christina Rosalie < crosa...@live.unc.edu> wrote: > Hi all, > > We wanted to explore adding automated tests for our locally developed > plugins and were curious how other institutions approached this. I know > ArchivesSpace has its own test suite that folks who develop on > ArchivesSpace can use, but how do institutions who develop their own > plugins test their custom functionality, especially when upgrading to a new > ASpace release? > > Thanks, > > Christina Cortland > Software Development > > UNC-Chapel Hill Libraries > > Pronouns: she/her > > ___ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group@lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderdur...@nypl.org ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
Re: [Archivesspace_Users_Group] Error? - Stanford upgrade from 1.5.4 to 2.6.0
Michael, Do you see anything interesting in the system logs or your browser's Javascript console when you try to open the collection? I don't see anything in the Extent record that you attached that would cause the Resource record to throw an error like that. Thanks, --Alex On Wed, Oct 16, 2019 at 3:25 PM Michael G Olson wrote: > Hi Steve, all, > > Sorry about that… the error message we’re receiving when we click on the > Collection tree is, "Oops! We're having trouble fetching this tree. > Please try refreshing the page.” > > If you open the image titled extent you'll see how our archivist entered > the extent for this particular collection. It looks like this isn't really > defined as a true child of the collection. > > thanks, > > Michael > > > -- > *From:* archivesspace_users_group-boun...@lyralists.lyrasis.org < > archivesspace_users_group-boun...@lyralists.lyrasis.org> on behalf of > Majewski, Steven Dennis (sdm7g) > *Sent:* Wednesday, October 16, 2019 12:15 PM > *To:* Archivesspace Users Group < > archivesspace_users_group@lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] Error? - Stanford upgrade from > 1.5.4 to 2.6.0 > > > Error messages/images are too compressed or small to read. Just a blur. > Can you resend or else transcribe ? — Steve M. > > > On Oct 16, 2019, at 2:52 PM, Michael G Olson wrote: > > Hi everyone, > > Here at Stanford Libraries we just ran an upgrade from 1.5.4 to version > 2.6.0 and noticed some odd behavior we’d like to validate with our peers. > We received no error messages while running the upgrade. That said, for > one of our repositories (we have many) we’ve noticed that by clicking on > the resource tree we get an error message. I’m speculating here but my > guess is that the extent for this resources were not defined in such a way > the application knows the relationship between parent and child. Here is > the error message we’re seeing. > > . > > For this particular example here is how our extents had been entered in > application. > > > > My questions are has anyone seen this sort of behavior before? Is this > something we can fix in the upgraded application or do we need to implement > a fix before the upgrade. Any insights anyone has on this issue would be > much appreciated! > > Michael > > > ___ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group@lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > ___ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group@lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderdur...@nypl.org ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
Re: [Archivesspace_Users_Group] public interface not displaying key finding aid data
Jessica, Do the missing Archival Objects and Note fields have their "Publish?" checkbox ticked off in the staff interface? If not, then they won't appear in the PUI. For the fields that are missing part of their information in the PUI, it could be that only some of the sub-notes have their "Publish?" boxes checked off; e.g., a Scope and Content note could have its "Publish?" box ticked off, but some of its sub-notes may not. If a collection doesn't have any information that you wouldn't want available via the PUI, you can use the "Publish All" button on the Resource screen to automatically check every "Publish?" box in a collection. If the missing notes are unpublished, then this will make them all available via the PUI. Thanks, --Alex On Thu, Aug 15, 2019 at 12:25 PM Jessica Wagner Webster < jessica.wagnerwebs...@baruch.cuny.edu> wrote: > Hi all, > > > > We've recently upgraded to v.2.5.2 and are starting to prepare our content > for access via the Public User Interface. I have several collection-level > records published so that I can see what they look like in the PUI. > However, for some reason, none of my records are displaying all of the > fields visible on the staff side- abstracts, biog/hist notes, etc. > Sometimes only some of those records are visible. Also, none of the records > have an active Collection Organization tab, even though many of them have > multiple series, subseries, and boxes/folders. I'm betting there's some > sort of box I haven't checked somewhere along the way, but I'm not sure how > to make this info visible. Any tips? Thanks. > > > > > > Jessica Wagner Webster > > Digital Initiatives Librarian, Assistant Professor > > Baruch College, Newman Library > > New York, NY 10010 > > jessica.wagnerwebs...@baruch.cuny.edu > > > ___ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group@lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderdur...@nypl.org ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
Re: [Archivesspace_Users_Group] barcode validation for ASpace
Benn, It's possible to validate barcodes for length via ASpace by modifying config.rb (ref. https://github.com/archivesspace/archivesspace/blob/master/docs/user/configuring-archivesspace.md). If the min and max values are set to the same length, then barcodes will only validate if they're either 0 or that exact length. You won't need to do anything elaborate to implement this - just add the correct values to config.rb and restart ASpace, and it'll immediately go into effect. I'm not aware of anything in ASpace that will do more elaborate validation (e.g. verifying that a barcode's check digits are correct); this would likely require either a plugin or feature request. Thanks, --Alex On Fri, Jun 21, 2019 at 1:39 PM Benn Joseph wrote: > Good afternoon, > > Over the past few years, our standard procedure when processing a new > collection has been to barcode the finished boxes and assign those barcodes > to their Top Containers in ASpace. > > > > ArchivesSpace does a great job of keeping a user from assigning a barcode > that has already been assigned elsewhere--which we recently discovered > after mistakenly being given a sheet of piggyback barcodes that had already > been assigned to various other collections. The system reports an error: > “Barcode – A barcode must be unique within a repository”. Great! > > > > One thing it doesn’t do is check for valid barcodes against a schema. For > instance, we try to be very careful about only using barcode scanners to > enter barcodes into ArchivesSpace, but every now and then one will get > entered by hand, or there will be an accidental keystroke after scanning. > In those cases, it would be ideal if ASpace were able to validate this > number to ensure that it’s correct (I understand that Alma does this using > a Codabar 13 validation routine, though there are other validation options > that would also look for a check digit). Would this be a plugin? A feature > request? Would it even be possible? > > > > The reason it’s important for us to ensure barcode accuracy is that a > large volume of our collections get sent offsite to a facility that uses > GFA as their inventory system. So, if we enter the barcode for a box that > is incorrect in ASpace and GFA records it differently, it ends up being > very difficult to recall that box if a researcher requests it. > > > > Thanks! > > --Benn > > > > *Benn Joseph* > > Head of Archival Processing > > Northwestern University Libraries > > Northwestern University > > www.library.northwestern.edu > > benn.jos...@northwestern.edu > > 847.467.6581 > _______ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group@lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderdur...@nypl.org ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
[Archivesspace_Users_Group] Components Out of Order in EAD/PDF
After updating our ASpace instance to 2.5.0, we've started to see odd behavior when exporting PDFs. Components will occasionally export in the wrong order in the PDF; for example, a recent collection exported with: Series I -- Subseries III [...subseries I components...] -- Subseries I [...subseries II components...] -- Subseries II --- [...subseries III components...] Strangely, while the subseries components are out of order, their children are in the correct location/order! This error has been intermittent; regenerating the PDF immediately resolves the issue. Unfortunately, this means that it has not been possible to reproduce the problem. Checking the logs, I did not see anything indicating an error in EAD or PDF generation from ASpace. I don't believe that the issue is in the EAD-to-PDF stylesheet, so I'm concerned that our EAD records may be generating with components in the wrong place in the finding aid. Has anyone else encountered issues like this? My suspicion is that https://github.com/archivesspace/archivesspace/blob/master/backend/app/exporters/models/ead.rb#L38 may be surfacing fleeting discrepancies between our search index and database, but it's difficult to tell, given how intermittent the issue is. Thanks, --Alex -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderdur...@nypl.org ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
Re: [Archivesspace_Users_Group] Extent Total
Danielle, It's probably possible to do this via SQL queries, but it would require a fairly complex query to effectively rebuild the Resource record. It would likely be easier to do this via requests against the API, which can return a list of all Resources in a repository; from there, you can query those Resources and extract their Extents. After logging in via the API, you can use this endpoint to get a list of all Resources in a given repository: https:// [your-ASpace-API-address-here]/repositories/[repository_id]/resources?all_ids=true (removing the brackets when substituting in your API address and repo ID) This will return a list of Resource IDs. You can pass each one to the Resource endpoint: https:// [your-ASpace-API-address-here]/repositories/[repository_id]/resources/[resource_id] (again, removing brackets) This will return the full JSON representation of the Resource. The extent metadata lives in the 'extents' field; from there, you can extract the information that you need (e.g. the extent number, container summary, extent type, etc.). Hope this helps - if you haven't worked with the API before, I'll be happy to send along tutorials/resources. Thanks! --Alex On Mon, Feb 25, 2019 at 6:05 PM Danielle Butler wrote: > I am trying to query our MySQL database to get a list of resource > identifiers with corresponding extent numbers. I have been fighting with it > for a while and I can get a list of extent numbers with no associated > resource information with included extents for accessions. With no apparent > way to discern which is which (I don’t want both accessions and resource > extent data because the data with be duplicative for processed > collections). I can get a list of resources, but without extent info. Does > anyone know of a way to get both out of the database? > > > > Thanks, > > > > Danielle Butler, CA | Archivist > > Butler Center for Arkansas Studies | Central Arkansas Library System > > www.butlercenter.org > > 100 Rock Street > > Little Rock, AR 72201 > > 501-320-5724 > > > ___ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group@lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderdur...@nypl.org ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
Re: [Archivesspace_Users_Group] diacritics in Title and Filing Title fields
Thanks for posting this! I created a ticket for this issue some time ago - https://archivesspace.atlassian.net/projects/ANW/issues/ANW-758. The issue appears to be that the base PDF font set is limited in its character support, and does not handle diacritics/non-Latin characters well - it either "flattens" them to ASCII, or replaces them with "#". I'm unaware of any workarounds in the meantime, but it's entirely a PDF rendering issue - your data should be fine as-is. Thanks, --Alex On Tue, Dec 11, 2018 at 12:57 PM Zalduendo, Ines wrote: > Thanks Benn for sending this along. > > The same is going on with Japanese characters. They display correctly in > ArchivesSpace but the PDF doesn’t display them. > > Here’s an example: > https://hollisarchives.lib.harvard.edu/repositories/7/resources/201 (top > right button for PDF) > > I never reported this to the users group, but am glad others are > interested in this being looked into. I was told core developers already > know about this. > > Ines > > > > Special Collections Archivist / Frances Loeb Library / Harvard University > Graduate School of Design / 48 Quincy Street, Cambridge, MA 02138 / T. > 617.496.1300 > > > > *From:* archivesspace_users_group-boun...@lyralists.lyrasis.org < > archivesspace_users_group-boun...@lyralists.lyrasis.org> *On Behalf Of *Benn > Joseph > *Sent:* Tuesday, December 11, 2018 11:19 AM > *To:* Archivesspace Users Group < > archivesspace_users_group@lyralists.lyrasis.org> > *Subject:* [Archivesspace_Users_Group] diacritics in Title and Filing > Title fields > > > > Not sure if there’s a ticket for this, but we’re seeing some tricky > behavior with diacritics in both the Title and Filing Title fields when > trying to print a PDF as a background job. > > > > Here’s an example: the collection name is “Camille Saint-Saëns > correspondence”, and the umlaut displays correctly in the public interface. > > > > If this text is input into the Title field without any character encoding, > i.e. if the “ë” is just pasted in there, then when I print a PDF as a > background job in the staff interface it shows up like this: > > > > “Camille Saint-Sae#ns correspondence” > > > > If I encode the character, whether HTML (ë) or UTF-8 (ë), the > title ends up looking like this in the PDF output: > > > > “Camille Saint-Saëns correspondence” > > > > …because the ampersand gets converted to “&” in the xml and ends up as > “& #235;”. I’m not seeing this behavior in any other fields though. > Does this mean that no diacritics are allowed in the Title fields? Or, am I > just inputting this wrong? When generating a PDF from the public interface, > it seems to remove the encoding entirely, so the title fields end up as > “Saint-Saens” in each case--although I understand that PDF creation process > to be different than the one done as a background job. > > > > Thanks! > > --Benn > > > > *Benn Joseph* > > Head of Archival Processing > > Northwestern University Libraries > > Northwestern University > > www.library.northwestern.edu > > benn.jos...@northwestern.edu > > 847.467.6581 > > > ___ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group@lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderdur...@nypl.org ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
Re: [Archivesspace_Users_Group] editing/adding series
Andrea, If you're looking to declare the level of hierarchy in the RDE, you can do so via the Level of Description column, which has a drop-down for Series, Subseries, File, etc. If you're looking to add hierarchy to the RDE (e.g. a row for a series, then rows for subseries/files under it), that's unfortunately impossible via the RDE. The RDE can only create components at one level at a time, so there's no way to create a series-level component and its children within a single RDE session. There are methods to create many components within a series via RDE (such as starting the RDE session from the series-level component), but there's no way to do so all within one single session. Hope this helps, --Alex On Fri, Nov 2, 2018 at 3:35 PM, Belair, Andrea wrote: > Hello, > I created a record and inputted via rapidentry at file level, and I'd like > to go back and add a column or hierarchical level to indicate series. Is > there a way to do this? I am not able to find it in my manual. > Thank you so much, > Andrea > > -- > Andrea Belair > Archives and Special Collections Librarian > Union College > 807 Union Street > Schenectady, NY 12308 > 518-388-6871 > > ___ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group@lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderdur...@nypl.org ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
Re: [Archivesspace_Users_Group] barcodes saga continues...
Lydia, You may want to take a look at NYU's MARC exporter plugin - https://github.com/NYULibraries/nyu_marcxml_export_plugin. This supports exporting item records via the 949 field, including container location, barcode, number, etc. ( https://github.com/NYULibraries/nyu_marcxml_export_plugin/blob/master/backend/lib/marc_custom_field_serialize.rb#L166 ). Depending on your ILS and local policies, you'll need to modify the mappings of ASpace data models to MARCXML via the plugin, but it should do what you're looking for. We use a modified version of the plugin here at the NYPL to generate our MARC + item records in the 949. I'm not aware of a MARC importer that will generate containers from item records, but it's not something that I've ever looked into. Thanks, --Alex On Fri, Aug 31, 2018 at 12:12 PM, Tang, Lydia wrote: > Hi all, > I have a wishful dream about barcoded top containers importing and > exporting out of our catalog system. Does anyone know of a plugin or tool > for enable this to happen? Example scenario: I have a collection with 60+ > barcoded containers nicely described in ArchivesSpace. I can easily export > the MARC record for the collection, but I just wish that it would also > export the item records for the barcoded top containers as well. This way, > when I import the MARCXML into my ILS, it also imports the barcoded and > attached item records. Ideally in the other direction, if a collection is > only described in MARC with attached barcoded item records for each box, > that could be imported into ArchivesSpace to create a stub resource record > with already created top containers. Is it possible? Has it been built? > Thanks, all! > > Lydia > -- > Dr. Lydia Tang, CA, DAS, DMA, MLIS > Special Collections Archivist-Librarian > Philosophy, Aesthetics, and Ethics Bibliographer > Michigan State University Libraries > 366 W. Circle Drive (DB 6) > East Lansing, MI 48824-1048 > Email: lta...@msu.edu > Phone: 517-884-8984 > ___ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group@lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderdur...@nypl.org ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
Re: [Archivesspace_Users_Group] Customizing generated citations for archival components
Lydia, Modifying the citation generation will require overriding/extending the current Archival Object data model ( https://github.com/archivesspace/archivesspace/blob/master/public/app/models/archival_object.rb#L33) - the .yml files aren't what control citation generation. The quick way to do so would be to create a plugin (in plugins/[plugin-name]/public/model/archival_object.rb) that overrides the cite function, and adding the plugin to your config/config.rb file's AppConfig[:plugins] line. It sounds like what you're trying to do should be straightforward, although you may have to get into the weeds of the JSON models to find the data that you need. Hope this helps, --Alex On Mon, Jul 30, 2018 at 12:58 PM, Tang, Lydia wrote: > Hi all, > My repository would like to tweak the data fields and the formatting of > the fully generated citations. Does anyone know how to do that? I assume it > would be in an en.yml file, but apparently there are three en.yml files and > my IT person is not sure where to look. Any help would be greatly > appreciated! Full description of our issue below: > > Current behavior on a sample citation: > Brooks, Marshall. Harry Smith, An Appreciation, 1936-2012. > The Smith collection, . Michigan State University Libraries Special > Collections. http://as.lib.msu.edu/repositories/2/archival_objects/24677 > Accessed July 11, 2018. > > A translation of the data fields: > [File title]. [Collection Title], . [Repository]. [Archival Object URI] > [Date accessed] > > What we’d like instead is added and bolded: > [Archival Object title], [Instance Information (Box/Folder number)], > [Collection title], [Collection identifier (such as MSS 212)], > [Repository]. [Archival Object URI] [Date accessed] > Ideally, we'd also like the citation to be formatted with commas instead > of periods as well. > Also, what are other ways repositories have editing their en.yml files? > We're just getting started in customizing and I wanted to get some ideas. > Thanks all! > Lydia > > Sent from my Verizon, Samsung Galaxy smartphone > ___ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group@lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderdur...@nypl.org ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
Re: [Archivesspace_Users_Group] Export to PDF Failing
Danielle, Wow! Thanks for sending this along - that's quite the PDF. Which version of ASpace are you using? Going through the listserv archives, some other folk were having similar issues on recent (2.x.x) versions of ASpace. If you can send me the EAD from ASpace (as-exported, pre-tweaks), I'll be happy to take a look at it and walk it through the PDF generation processes. ASpace generates its PDF finding aids by generating and transforming the EAD XML, so the EAD is usually the first place to look when the PDF is misbehaving. Thanks, --Alex On Mon, Jul 23, 2018 at 2:48 PM, Danielle Butler wrote: > Hello Alex, > > > > I’m not getting any errors from the background job, but the PDF it creates > is malformed and missing most of the components. I’ve attached a screenshot > of the background job results and the PDF it generated. > > > > And the EAD I get from export has to have some small tweaks made, but it > validates and works in our XSL stylesheet. > > > > *From:* archivesspace_users_group-boun...@lyralists.lyrasis.org [mailto: > archivesspace_users_group-boun...@lyralists.lyrasis.org] *On Behalf Of > *Alexander > Duryee > *Sent:* Monday, July 23, 2018 1:40 PM > *To:* Archivesspace Users Group lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] Export to PDF Failing > > > > Danielle, > > > > Is the PDF exporter throwing an error within ASpace, or is it completing > the export but returning a malformed PDF? Could you provide an example of > how it's failing? > > > > When you export EAD, does it validate against the EAD schema / as > well-formed XML? > > > > Thanks, > > --Alex > > > > > > On Mon, Jul 23, 2018 at 1:35 PM, Danielle Butler wrote: > > We recently migrated all of our data from Toolkit to ASpace. Everything > seems to have migrated fine, and we get clean EAD on export, but I cannot > get the print to PDF function to give me anything functional. > > > > I looked through the archives and didn’t find an answer to this issue. > > > > Thanks, > > > > Danielle Butler, CA | Archivist > > Butler Center for Arkansas Studies | Central Arkansas Library System > > www.butlercenter.org > > 100 Rock Street > > Little Rock, AR 72201 > > 501-320-5724 > > > > > ___ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group@lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > > -- > > Alexander Duryee > > Metadata Archivist > > New York Public Library > > (917)-229-9590 > > alexanderdur...@nypl.org > > ___ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group@lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderdur...@nypl.org ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
Re: [Archivesspace_Users_Group] Export to PDF Failing
Danielle, Is the PDF exporter throwing an error within ASpace, or is it completing the export but returning a malformed PDF? Could you provide an example of how it's failing? When you export EAD, does it validate against the EAD schema / as well-formed XML? Thanks, --Alex On Mon, Jul 23, 2018 at 1:35 PM, Danielle Butler wrote: > We recently migrated all of our data from Toolkit to ASpace. Everything > seems to have migrated fine, and we get clean EAD on export, but I cannot > get the print to PDF function to give me anything functional. > > > > I looked through the archives and didn’t find an answer to this issue. > > > > Thanks, > > > > Danielle Butler, CA | Archivist > > Butler Center for Arkansas Studies | Central Arkansas Library System > > www.butlercenter.org > > 100 Rock Street > > Little Rock, AR 72201 > > 501-320-5724 > > > > ___ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group@lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderdur...@nypl.org ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
[Archivesspace_Users_Group] ArchivesSpace Solr 4 -> Solr 6
We'd like to upgrade our Solr instances to Solr 6, including our ArchivesSpace Solr instance (currently 4.6.0). Looking into what this would require, it looks like we'll need to tweak Solr to either use managed-schema or point it at an updated schema.xml. Beyond this, though, it's not clear if anything needs to be changed on ASpace's end. Has anyone upgraded ASpace to use Solr 6, and if so, what needed to be changed within the Solr core / schema / ASpace instance? Thanks! --Alex -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderdur...@nypl.org ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
Re: [Archivesspace_Users_Group] [archivesspace] Request for community input: ANW-380
subrecord* >> >> Date Expression: circa 1950-1960 >> >> … >> >> Begin: 1950 >> >> End: 1960 >> >> Certainty: Approximate >> >> >> >> The revised model would include a separate date expression field entry >> for each part of the date span: >> >> >> >> *Date subrecord* >> >> Begin Date Expression: circa 1950 >> >> … >> >> Begin Date Standardized: 1950 >> >> >> >> End Date Expression: 1960 >> >> … >> >> End Date Standardized: 1960 >> >> … >> >> Certainty: Approximate >> >> >> >> The concern has been raised that institutions may not have sufficiently >> consistent data entry practices to allow a single migration script to parse >> existing Date Expression values into separate Begin and End date expression >> fields. One proposed path has been to move the entire existing Date >> Expression value to the new Begin Date Expression, while moving the >> normalized dates to their appropriate standardized value fields. This would >> appear as: >> >> >> >> *Date subrecord* >> >> Begin Date Expression: circa 1950-1960 >> >> … >> >> Begin Date Standardized: 1950 >> >> >> >> End Date Expression: >> >> … >> >> End Date Standardized: 1960 >> >> … >> >> Certainty: Approximate >> >> >> >> The Development Prioritization Team would like to obtain feedback from >> the community regarding preferences for migrating existing Date subrecord >> content, or other concerns. Comments may be submitted through JIRA on the >> ticket for ANW-380 (https://archivesspace.atlassian.net/browse/ANW-380). >> >> >> >> Sincerely, >> >> >> >> Cory Nimer >> >> University Archivist >> >> Brigham Young University >> >> 801-422-6091 >> >> -- >> You received this message because you are subscribed to the Google Groups >> "ArchivesSpace" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to archivesspace+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > chris fitzpatrick > http://cfitz.github.io/ > > -- > You received this message because you are subscribed to the Google Groups > "ArchivesSpace" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to archivesspace+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderdur...@nypl.org ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
Re: [Archivesspace_Users_Group] Configuring barcode digits?
Mark,
Thanks! I wasn't aware that these features were documented in the old
plugin repo.
I added documentation on container management options to config.rb (
https://github.com/archivesspace/archivesspace/commit/8ffeed29dd35649a2cf26bd908fb12794a803b22),
and the tech-docs repo will be updated with documentation as well. They'll
be less secret in future releases :)
Thanks again!
--Alex
On Fri, Mar 16, 2018 at 1:38 PM, Rachel Aileen Searcy wrote:
> Thanks, everyone!
>
> On Fri, Mar 16, 2018 at 1:01 PM, Custer, Mark
> wrote:
>
>> Rachel, all:
>>
>>
>>
>> It was documented in the plugin. I still refer to that documentation
>> here:
>>
>>
>>
>> https://github.com/hudmol/container_management#configuring-it
>>
>>
>>
>> But it should be added to the core documentation, of course!
>>
>>
>>
>> Mark
>>
>>
>>
>>
>>
>>
>>
>> *From:* archivesspace_users_group-boun...@lyralists.lyrasis.org [mailto:
>> archivesspace_users_group-boun...@lyralists.lyrasis.org] *On Behalf Of
>> *Alexander
>> Duryee
>> *Sent:* Friday, 16 March, 2018 12:40 PM
>> *To:* Archivesspace Users Group > alists.lyrasis.org>
>> *Subject:* Re: [Archivesspace_Users_Group] Configuring barcode digits?
>>
>>
>>
>> Rachel,
>>
>> It's an undocumented feature in config/config.rb. You'll need to add the
>> following line, swapping our values for yours and expanding as needed:
>>
>> AppConfig[:container_management_barcode_length] = {"MSS" => {:min => '14',
>> :max => '14'}, "THE" => {:min => '14', :max => '14'}}
>>
>> Note that this uses the repository code to match the validation to its
>> repository. If a container has no barcode, it automatically validates -
>> for our case, barcodes must be exactly either 0 or 14 characters long.
>>
>>
>>
>> (Code here - https://github.com/archivesspace/archivesspace/blob/master/
>> common/barcode_check.rb
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_archivesspace_archivesspace_blob_master_common_barcode-5Fcheck.rb&d=DwMFaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=Pnnmkh2-cdIM86hiV2KtNoFYhuE0Tpjadc-sitAkIeI&s=KARazaCqWnjXQCGHbS8--dmdJ3MoW1DqkrQtS5hfrJ4&e=>
>> )
>>
>> Hope this helps,
>>
>> --Alex
>>
>>
>>
>> On Fri, Mar 16, 2018 at 11:31 AM, Rachel Aileen Searcy <
>> rachel.sea...@nyu.edu> wrote:
>>
>> Hello everyone,
>>
>>
>>
>> We're interested in configuring the barcode field of the top container
>> record to enforce validation for the number of digits. It looks like this
>> was included in the original development of the container management
>> functionality
>> <https://guides.library.yale.edu/archivesspace/ASpaceContainerManagement>,
>> but after poking around a bit in the system and available documentation I
>> don't see any further information. If anyone has done this locally, could
>> you be so kind as to tell me how you made this happen?
>>
>>
>>
>> Thanks very much (and in the spirit of the season, go raibh maith agat 🍀
>> ),
>>
>>
>>
>> Rachel Searcy
>> Accessioning Archivist, Archival Collections Management
>>
>> New York University Libraries
>>
>> 212.998.2539 <(212)%20998-2539> | rachel.sea...@nyu.edu
>>
>>
>> ___
>> Archivesspace_Users_Group mailing list
>> Archivesspace_Users_Group@lyralists.lyrasis.org
>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwMFaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=Pnnmkh2-cdIM86hiV2KtNoFYhuE0Tpjadc-sitAkIeI&s=xrIwQ0MnD7X5E5Ky-n6c4pWnAeKe4VP0GAybT_Tm6Bg&e=>
>>
>>
>>
>>
>> --
>>
>> Alexander Duryee
>>
>> Metadata Archivist
>>
>> New York Public Library
>>
>> (917)-229-9590 <(917)%20229-9590>
>>
>> alexanderdur...@nypl.org
>>
>> ___
>> Archivesspace_Users_Group mailing list
>> Archivesspace_Users_Group@lyralists.lyrasis.org
>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>>
>>
>
>
> --
> Rachel Searcy
> Accessioning Archivist, Archival Collections Management
> New York University Libraries
> 212.998.2539 | rachel.sea...@nyu.edu
>
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>
--
Alexander Duryee
Metadata Archivist
New York Public Library
(917)-229-9590
alexanderdur...@nypl.org
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
Re: [Archivesspace_Users_Group] Configuring barcode digits?
Rachel,
It's an undocumented feature in config/config.rb. You'll need to add the
following line, swapping our values for yours and expanding as needed:
AppConfig[:container_management_barcode_length] = {"MSS" => {:min => '14',
:max => '14'}, "THE" => {:min => '14', :max => '14'}}
Note that this uses the repository code to match the validation to its
repository. If a container has no barcode, it automatically validates -
for our case, barcodes must be exactly either 0 or 14 characters long.
(Code here -
https://github.com/archivesspace/archivesspace/blob/master/common/barcode_check.rb
)
Hope this helps,
--Alex
On Fri, Mar 16, 2018 at 11:31 AM, Rachel Aileen Searcy <
rachel.sea...@nyu.edu> wrote:
> Hello everyone,
>
> We're interested in configuring the barcode field of the top container
> record to enforce validation for the number of digits. It looks like this
> was included in the original development of the container management
> functionality
> <https://guides.library.yale.edu/archivesspace/ASpaceContainerManagement>,
> but after poking around a bit in the system and available documentation I
> don't see any further information. If anyone has done this locally, could
> you be so kind as to tell me how you made this happen?
>
> Thanks very much (and in the spirit of the season, go raibh maith agat 🍀),
>
> Rachel Searcy
> Accessioning Archivist, Archival Collections Management
> New York University Libraries
> 212.998.2539 | rachel.sea...@nyu.edu
>
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>
--
Alexander Duryee
Metadata Archivist
New York Public Library
(917)-229-9590
alexanderdur...@nypl.org
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
Re: [Archivesspace_Users_Group] Linking Agents to Archival Objects
Lynn, Which version are you encountering this issue on? I tried reproducing this issue on the sandbox ( http://sandbox.archivesspace.org/resources/11/edit#tree::resource_11, username/password are admin/admin), but the PDF didn't cause any issues. Thanks! --Alex On Mon, Mar 12, 2018 at 2:47 PM, Lynn Moulton wrote: > A correction: that query should have read "link some subject names" to the > archival object. Agents with the role "creator" don't cause a problem, but > Agents with the role set to "subject" do. > > ___ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group@lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderdur...@nypl.org ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
Re: [Archivesspace_Users_Group] Editing linked agent roles
Adam, Last year, we temporarily made this list editable to add a new value, suppressed the Source entry, then reset it to being read-only. We haven't encountered any ill effects yet, although we also edited the MARCXML and EAD exporters to account for the new entries. Regards, --Alex On Thu, Mar 8, 2018 at 11:05 AM, Adam Jazairi wrote: > Hi all, > > I was going to create a new value for the Linked Agent Role controlled > value list, but I saw that the database has disabled the editing of that > list. Would it cause problems with the application if I temporarily made > Linked Agent Role editable? > > Thanks, > > Adam > > -- > Adam Jazairi > Digital Library Applications Developer > Boston College > (617) 552-1404 > adam.jaza...@bc.edu > > ___ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group@lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderdur...@nypl.org ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
Re: [Archivesspace_Users_Group] Export PDF and EAD
Tara, Do you have an example of the bad EAD output? Thanks, --Alex On Wed, Sep 20, 2017 at 9:42 AM, Hurt, Tara (Library) wrote: > Good morning everyone. > > > > Thank you for all the advice on our migration from 1.4.2 …… we are running > 2.1.2 now. > > > > Anyone who is using 2.1.2, are you having trouble generating PDF and EAD > in the Export function? > > > > We are having trouble …. It looks like the output is all garbled and not > consistent in any collection. > > > > Is this a known problem and the fix is in the works now? > > > > Tara L. Hurt > > ___ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group@lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderdur...@nypl.org ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
Re: [Archivesspace_Users_Group] Barcodes Disappearing from Database
Following up on this, we were able to identify the issue. What appeared to be data loss on the backend was caused by an interface issue on the frontend, in which barcodes were not being carried through into the Rapid Barcode Entry screen. To replicate this issue: - Open Manage Top Containers, select a number of containers, and open Rapid Barcode Entry - Enter barcodes for the containers and save. This will take you back to the Manage Top Containers screen with your containers still selected. - Wait a few minutes, so that the barcodes will have propagated into the index - Open Rapid Barcode Entry for the containers that you previously selected - Despite the containers having saved barcodes, and the barcodes being indexed, the Rapid Barcode Entry screen will not display the barcodes! As a workaround, refresh the Manage Top Containers screen before re-opening Rapid Barcode Entry. Thanks, --Alex On Fri, Jul 14, 2017 at 5:12 PM, Alexander Duryee wrote: > We've started assigning barcodes in bulk via the Manage Top Containers > screen, and have run into a troubling issue. Assigning barcodes to Top > Containers via the Rapid Barcode Entry screen has gone well; however, > ranges of barcodes (typically the last set done at once) will disappear > from the application without warning. Examining the system log reveals > that the barcodes were not removed via the frontend or API - there are no > API calls that would have assigned a blank value to the containers. More > perplexing, the missing barcodes do not manifest in the index - searching > the barcodes via the Manage Top Container screen would show them as being > present, but checking the container directly (or the backend database) > shows no barcode. It's as if the data simply disappeared, with no obvious > cause. > > NYPL has created a number of custom plugins, so it's not impossible that > one of them is causing the issue. However, none of our plugins directly > modify the TopContainer model, so I doubt that one of them is causing the > issue. We're on 1.5.1 still. > > Has anyone else encountered an issue like this, or is there something I > should be on the lookout for that could be impacting our data? > > Thanks! > --Alex > > -- > Alexander Duryee > Metadata Archivist > New York Public Library > (917)-229-9590 <(917)%20229-9590> > alexanderdur...@nypl.org > -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderdur...@nypl.org ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
[Archivesspace_Users_Group] Barcodes Disappearing from Database
We've started assigning barcodes in bulk via the Manage Top Containers screen, and have run into a troubling issue. Assigning barcodes to Top Containers via the Rapid Barcode Entry screen has gone well; however, ranges of barcodes (typically the last set done at once) will disappear from the application without warning. Examining the system log reveals that the barcodes were not removed via the frontend or API - there are no API calls that would have assigned a blank value to the containers. More perplexing, the missing barcodes do not manifest in the index - searching the barcodes via the Manage Top Container screen would show them as being present, but checking the container directly (or the backend database) shows no barcode. It's as if the data simply disappeared, with no obvious cause. NYPL has created a number of custom plugins, so it's not impossible that one of them is causing the issue. However, none of our plugins directly modify the TopContainer model, so I doubt that one of them is causing the issue. We're on 1.5.1 still. Has anyone else encountered an issue like this, or is there something I should be on the lookout for that could be impacting our data? Thanks! --Alex -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderdur...@nypl.org ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
Re: [Archivesspace_Users_Group] Intermittent Outages
Chelsea, Thanks for your response! We aren't seeing any resource usage spikes during/before outages, and the disk isn't filling up, so that isn't the issue on our end. We've already limited ASpace to our internal network, so it's not a question of extreme traffic. Thanks, --Alex On Tue, Feb 28, 2017 at 12:47 PM, Chelsea Lobdell wrote: > Hi Alex, > > Not sure if this is going to be helpful or not but we were seeing a lot of > CPU load warnings on our dev server that would bring the frontend of the > application to a grinding halt until it was restarted. I was unable to see > anything in the logs or any sort of malicious traffic so I put a few stop > gaps in place. First, I adjusted IP Table and Firewall rules to lock down > the application to only campus IP ranges. The application is only used by > staff currently and they know if they are coming from off campus they need > to use EZProxy or VPN for access. Secondly, I set a nightly restart cron > from the root user's crontab: > # restart archivesspace every night at 2am > 00 02 * * * /etc/init.d/archivesspace stop > 05 02 * * * /etc/init.d/archivesspace start > > We haven't experience CPU load warnings since I put these stop gaps in > place. So I'm still uncertain of what was causing the issue but maybe these > stop gaps can help you too. > > - Chelsea > > *---* > *Chelsea Lobdell* > *Library Web Developer/ Swarthmore College* > *clobd...@swarthmore.edu / (610)690-6818 > <(610)%20690-6818>* > > On Tue, Feb 28, 2017 at 12:27 PM, Alexander Duryee < > alexanderdur...@nypl.org> wrote: > >> Our production instance of ASpace has been suffering from intermittent >> outages for the past few weeks. Roughly once or twice a day, the >> application will go down for 1-5 minutes, then bring itself back up. >> Perplexingly, this doesn't seem to impact the backend - for example, the >> application went down during a reindex, but the reindex continued (and was >> logged) during the outage. However, API requests are dropped and the >> frontend is inaccessible during the outage. >> >> We haven't identified a cause for the outages (e.g. heavy traffic, lots >> of database calls), as there's no consistent pattern. There's nothing in >> archivesspace.out to indicate any troubles. >> >> Has anyone else experienced similar issues? Is there another log that we >> could refer to (e.g. ASpace's Apache instance) to diagnose the outages? >> >> Thanks! >> --Alex >> >> -- >> Alexander Duryee >> Metadata Archivist >> New York Public Library >> (917)-229-9590 <(917)%20229-9590> >> alexanderdur...@nypl.org >> >> ___ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group@lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> > > ___ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group@lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderdur...@nypl.org ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
[Archivesspace_Users_Group] Intermittent Outages
Our production instance of ASpace has been suffering from intermittent outages for the past few weeks. Roughly once or twice a day, the application will go down for 1-5 minutes, then bring itself back up. Perplexingly, this doesn't seem to impact the backend - for example, the application went down during a reindex, but the reindex continued (and was logged) during the outage. However, API requests are dropped and the frontend is inaccessible during the outage. We haven't identified a cause for the outages (e.g. heavy traffic, lots of database calls), as there's no consistent pattern. There's nothing in archivesspace.out to indicate any troubles. Has anyone else experienced similar issues? Is there another log that we could refer to (e.g. ASpace's Apache instance) to diagnose the outages? Thanks! --Alex -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderdur...@nypl.org ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
[Archivesspace_Users_Group] Hiding Controlled Date Fields
Since implementing automated date parsing in ASpace and our discovery system, we don't have a local need for the controlled date fields in ASpace's Date sub-form. As such, we'd like to prevent the controlled date fields from spawning in the data entry interface via a plug-in. It seems that the subforms are generated by dates.crud.js, which creates the forms upon the user selecting a date type. I'm not quite certain how to remove/override this bit of JavaScript via a plug-in - I tried modifying the JS and saving the file to plugins/my-plugin/frontend/assets/, but to no avail. Is this the right approach to override the script's behavior, or is there another tack I should be taking? More ambitiously, we'd like to only show the controlled date subform to users above a certain permission level. We were able to implement this for non-JS forms in the user interface (via user_can? checks), but I'm not clear as to how this can be done for JS events. Is this possible, and if so, what would need to be modified? Thanks! --Alex -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderdur...@nypl.org ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
[Archivesspace_Users_Group] Issues Importing/Rearranging Large Collection
We were able to successfully import a large collection (~2000 components) into ArchivesSpace, and imported a set of additions to the collection as well. However, after importing the additions, we ran into two problems: 1) After importing the additions via the API, many of the archival objects also have additional "ghost" records in the tree view. These records are just pointers to the "real" object - clicking them opens the correct object - but they cannot be moved/deleted from the collection. In addition, these records are exporting in the EAD XML output (as copies of the "real" record). Most perplexingly, these ghost records don't appear as archival objects in the backend database - only via the frontend and exports. 2) When rearranging archival objects within the collection (via the tree view), the object first appears in the proper location. However, when refreshing the collection, the component appears 5-10 objects away from where it was dropped. This is reinforced by the object's position value in the database - for example, drag-and-dropping an object to position 205 will save it at position 198 instead. Any ideas as to causes/solutions/workarounds would be tremendously appreciated. Many thanks! --Alex -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderdur...@nypl.org ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
[Archivesspace_Users_Group] Announcing Two Plugins
All, I'd like to announce the release of two plugins for ArchivesSpace: multiple_identifiers (https://github.com/alexduryee/multiple_identifiers) extends the ArchivesSpace data model to provide a repeatable identifier element. Currently, ArchivesSpace supports up to one identifier per resource/archival object, which was insufficient for our descriptive needs. This plugin allows for multiple identifiers to be provided to each object (as type/value pairs), as well as supporting EAD export via the element. timewalk (https://github.com/alexduryee/timewalk) provides automated date parsing for Date expressions in ArchivesSpace. When saving a freetext date expression with no Begin/End values, ArchivesSpace will now attempt to automatically parse the expression and provide Begin/End values based on the input (e.g. "September 1999 - March 2000" will translate into a Begin of "1999-09" and an End of "2000-03"). Any feedback, issues, or pull requests are much appreciated! Thanks, --Alex -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderdur...@nypl.org ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
Re: [Archivesspace_Users_Group] Plugin Gem Best Practices
Mark, That resolved the issue - many thanks! --Alex On Fri, Nov 4, 2016 at 6:09 AM, Mark Triggs wrote: > Hi Alex, > > This is a bit of a shot in the dark, but for the Newrelic gem I found I > had to add a snippet to the top of the plugin Gemfile like this: > > https://github.com/archivesspace/archivesspace/pull/183/files > > The call to `ASpaceGems.setup` takes care of setting the gem load path > appropriately. > > You're not supposed to have to do this, so if you find it magically fixes > things, I'll take a look and see if the situation can be improved. The > backend is supposed to take care of all of this, but perhaps the Gemfile is > being loaded earlier than expected. > > Cheers, > > Mark > > Alexander Duryee writes: > > James, > > Thanks! I unzipped a fresh release of ASpace, set up a plugin with a > Gemfile, and ran initialize_plugin. It pulled in the gem + dependencies > into gems/ without issue. However, when trying to run ASpace with the > plugin (empty except for the gems), I got: > > Bundler::GemNotFound: Could not find gem 'timetwister (= 0.2.7) java' in > any of the gem sources listed in your Gemfile or available on this machine. > > The gem is installed both on my machine and in the plugin's gems > directory. It's a locally-developed gem, so I didn't explicitly build it > for JRuby - is this necessary to load it into ASpace? > > Thanks! > --Alex > > -- > Mark Triggs > > > -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderdur...@nypl.org ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
Re: [Archivesspace_Users_Group] Plugin Gem Best Practices
James, Thanks! I unzipped a fresh release of ASpace, set up a plugin with a Gemfile, and ran initialize_plugin. It pulled in the gem + dependencies into gems/ without issue. However, when trying to run ASpace with the plugin (empty except for the gems), I got: Bundler::GemNotFound: Could not find gem 'timetwister (= 0.2.7) java' in any of the gem sources listed in your Gemfile or available on this machine. The gem is installed both on my machine and in the plugin's gems directory. It's a locally-developed gem, so I didn't explicitly build it for JRuby - is this necessary to load it into ASpace? Thanks! --Alex On Wed, Nov 2, 2016 at 6:37 PM, James Bullen wrote: > > Hi Alex, > > There’s a script for this. Try this from your aspace directory: > > scripts/initialize_plugin.sh [plugin_name] > > > … .bat if you’re on windows. > > > Good luck! > > > James > > > On Nov 3, 2016, at 6:46 AM, Alexander Duryee > wrote: > > I'd like to use a third-party plugin in an ASpace plugin; however, I'm > running into issues with ASpace loading the gem. I've tried copying the > structure from the OCLC plugin (gems/ directory containing the gem, > plugin_init.rb loading the directory into $LOAD_PATH), but to no avail. > What are the best practices for including a gem in a plugin, ideally for > distribution? > > Thanks! > --Alex > > -- > Alexander Duryee > Metadata Archivist > New York Public Library > (917)-229-9590 > alexanderdur...@nypl.org > !DSPAM:581a4296162421185191756! __ > _ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group@lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > !DSPAM:581a4296162421185191756! > > > > ___ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group@lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderdur...@nypl.org ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
[Archivesspace_Users_Group] Plugin Gem Best Practices
I'd like to use a third-party plugin in an ASpace plugin; however, I'm running into issues with ASpace loading the gem. I've tried copying the structure from the OCLC plugin (gems/ directory containing the gem, plugin_init.rb loading the directory into $LOAD_PATH), but to no avail. What are the best practices for including a gem in a plugin, ideally for distribution? Thanks! --Alex -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderdur...@nypl.org ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
Re: [Archivesspace_Users_Group] Creating enumeration values via API
Dallas, Many thanks! This worked perfectly. Thanks again, --Alex On Fri, Oct 21, 2016 at 2:24 PM, Dallas Pillen wrote: > Hi Alexander, > > We had a script that did just that using the update enumeration endpoint > (POST /config/enumerations/:enum_id) by first getting the enumeration's > JSON object, adding new enumeration values to the enumeration's "values" > array, and posting the updated JSON (see example gist > <https://gist.github.com/djpillen/4dd8f3b2e4672a1874c8ac8c646037db>). > This handles the creation of new enumeration_values; they do not need to be > created separately. > > On Fri, Oct 21, 2016 at 2:01 PM, Alexander Duryee < > alexanderdur...@nypl.org> wrote: > >> As part of our deployment process, I would like to have a script that >> automatically adds new enumeration values to certain enumerations. >> Querying on the /config/enumerations/:enumeration_id endpoint returns a >> JSON object that ensconces a number of enumeration_value objects, so it >> seems like I need to create the enumeration_value, then add that to the >> enumeration. However, there seem to be no endpoints for creating new >> enumeration_value objects. Is there another method that I should be using >> to create/update enumerations with new values via the API? >> >> Thanks, >> --Alex >> >> -- >> Alexander Duryee >> Metadata Archivist >> New York Public Library >> (917)-229-9590 >> alexanderdur...@nypl.org >> >> ___ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group@lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> > > > -- > > *Dallas Pillen*Assistant Archivist for Metadata and Digital Projects > > > Bentley Historical Library <http://bentley.umich.edu/> > 1150 Beal Avenue > Ann Arbor, Michigan 48109-2113 > 734.647.3559 > Twitter <https://twitter.com/umichBentley> Facebook > <https://www.facebook.com/bentleyhistoricallibrary> > > ___ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group@lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderdur...@nypl.org ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
[Archivesspace_Users_Group] Creating enumeration values via API
As part of our deployment process, I would like to have a script that automatically adds new enumeration values to certain enumerations. Querying on the /config/enumerations/:enumeration_id endpoint returns a JSON object that ensconces a number of enumeration_value objects, so it seems like I need to create the enumeration_value, then add that to the enumeration. However, there seem to be no endpoints for creating new enumeration_value objects. Is there another method that I should be using to create/update enumerations with new values via the API? Thanks, --Alex -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderdur...@nypl.org ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
