[Archivesspace_Users_Group] Guidance for Human Readable URLs

Wed Aug 3 12:36:24 EDT 2022

Hello Brian,

You are correct that, even when human readable URLs are turned on, the slugs field is only populated when a new record is created or when an existing record is opened and updated.

The Generate Slugs in Bulk background job is to populate the slugs field for all of the relevant records in the database. Once you enable human readable URLs in your configuration settings, that background job will appear in the list of background jobs for people with sufficient permissions.

[cid:image002.png at 01D8A735.41BB2A40]
[cid:image003.png at 01D8A735.A36B1980]
It uses your configuration settings for generating individual slugs.

From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Duckett, Brian (NIH/NLM) [C]
Sent: Wednesday, August 3, 2022 11:55 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Cc: Liu, Steve (NIH/NLM) [C] <steve.liu at nih.gov>; Whitaker, John (NIH/NLM) [C] <john.whitaker at nih.gov>; Kalyanasundaram, Sriram (NIH/NLM) [C] <sriram.kalyanasundaram at nih.gov>
Subject: Re: [Archivesspace_Users_Group] Guidance for Human Readable URLs

Hello Christine,

Thank You again for the wiki link.
After some investigation we have narrowed the issue we are experiencing:

  *   Slugs are null  In the database even though the is_slug_auto  column in the database is true (set to 1)

There are references to a `background job` in the wiki documentation. I am hoping you can clarify when and how the background job is run, as well as if this is the process that will correct the issue noted above.

We have done some troubleshooting.

  *   When editing the resource, simple pressing save will populate the slug
  *   Dropping and Re-Importing the entire database corrects the issue also

Thank You,
Brian Duckett
Cloud Developer, AWS Developer Associate, AWS DevOps Professional
(Contractor, GDIT)
National Library of Medicine, OCCS/OD

From: Duckett, Brian (NIH/NLM) [C]<mailto:brian.duckett at nih.gov>
Sent: Friday, July 29, 2022 3:46 PM
To: Archivesspace Users Group<mailto:archivesspace_users_group at lyralists.lyrasis.org>
Cc: Kalyanasundaram, Sriram (NIH/NLM) [C]<mailto:sriram.kalyanasundaram at nih.gov>; Whitaker, John (NIH/NLM) [C]<mailto:john.whitaker at nih.gov>; Liu, Steve (NIH/NLM) [C]<mailto:steve.liu at nih.gov>
Subject: RE: Guidance for Human Readable URLs

Hello Christine,

Thank You. The information in the wiki is exactly what we are looking for.

Thank You,
Brian Duckett
Cloud Developer, AWS Developer Associate, AWS DevOps Professional
(Contractor, GDIT)
National Library of Medicine, OCCS/OD

From: Christine Di Bella<mailto:christine.dibella at lyrasis.org>
Sent: Thursday, July 28, 2022 11:52 AM
To: Archivesspace Users Group<mailto:archivesspace_users_group at lyralists.lyrasis.org>
Cc: Kalyanasundaram, Sriram (NIH/NLM) [C]<mailto:sriram.kalyanasundaram at nih.gov>; Whitaker, John (NIH/NLM) [C]<mailto:john.whitaker at nih.gov>; Liu, Steve (NIH/NLM) [C]<mailto:steve.liu at nih.gov>
Subject: [EXTERNAL] Re: [Archivesspace_Users_Group] Guidance for Human Readable URLs

Hello Brian,

Have you looked at the user manual section on this feature: https://archivesspace.atlassian.net/wiki/spaces/ArchivesSpaceUserManual/pages/890208314/Human-Readable+URLs<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Farchivesspace.atlassian.net%2Fwiki%2Fspaces%2FArchivesSpaceUserManual%2Fpages%2F890208314%2FHuman-Readable%2BURLs&data=05%7C01%7Cbrian.duckett%40nih.gov%7Cfd699b5275a14072694808da70b136c3%7C14b77578977342d58507251ca2dc2b06%7C0%7C0%7C637946203691980389%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=KRRS8CrvrC6Y4WEpbSXYBOAW6xofgWg9YSh%2FHzyV87U%3D&reserved=0>? If not, that would be a good place to start for an overview.

Hopefully some folks on here can give more advice from the point of view of actual implementations.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
678-235-2905

[ASpaceOrgHomeMedium]

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> On Behalf Of Duckett, Brian (NIH/NLM) [C]
Sent: Tuesday, July 26, 2022 2:03 PM
To: archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>
Cc: Liu, Steve (NIH/NLM) [C] <steve.liu at nih.gov<mailto:steve.liu at nih.gov>>; Whitaker, John (NIH/NLM) [C] <john.whitaker at nih.gov<mailto:john.whitaker at nih.gov>>; Kalyanasundaram, Sriram (NIH/NLM) [C] <sriram.kalyanasundaram at nih.gov<mailto:sriram.kalyanasundaram at nih.gov>>
Subject: [Archivesspace_Users_Group] Guidance for Human Readable URLs

Hello,

We are requesting guidance on how to implement human readable URLs in the ArchivesSpace application.

Our production instance supports this to an extent. For example, the following listed URL is a "human readable" URL for the standard ArchivesSpace URL https://archivesspace.nlm.nih.gov/repositories/4/resources/968

  *   https://archivesspace.nlm.nih.gov/repositories/ammp/resources/__101576736

We would like to implement this naming standard across all public facing links. Guidance on integrating this implementation for search would also be highly appreciated.

Thank You,
Brian
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and are confident the content is safe.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20220803/9f71ac78/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 8792 bytes
Desc: image001.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20220803/9f71ac78/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 100441 bytes
Desc: image002.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20220803/9f71ac78/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 271032 bytes
Desc: image003.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20220803/9f71ac78/attachment-0003.png>