[Archivesspace_Users_Group] Previous archival resource keys in PDF?

[Andrew Morrison]

It sounds like you missed this new config file option in the 3.3.0 
release notes:

/+# Prior to 3.2.0, multiple ARKs may have been created without//
//+# the user intending to do so. Setting this to true will make//
//+# database upgrade 158 attempt to clean up unwanted extra ARKs.//
//+# When multiple rows in the ARK table reference the same resource//
//+# or archival object, the first one created will be kept//
//+# and the rest discarded.//
//+# Use with caution and test thoroughly.//
//+AppConfig[:prune_ark_name_table] = false/

But if you didn't know you had this problem when you were upgrading, you 
wouldn't have known that you needed to enable it. Unfortunately, setting 
it to true now won't do anything. The code it would've run is in 
database migration 158, which cannot be re-run a second time. It would 
probably be best to get in touch with Lyrasis, or your service provider 
if using a hosted system, to get help with your specific situation.

Andrew.


On 28/09/2023 21:21, Jane LaBarbara wrote:
>
> All,
>
> We have this issue where our PDFs of resource records sometimes have a 
> lot of previous archival resource keys showing us as “ID 
> [ark-superseded]” – I included one page, extracted from a PDF, as an 
> example of the problem. That collection actually has two pages of 
> these arks (30 previous ones are listed).
>
> I’m assuming ARKs getting superseded like this has something to do 
> with the OAI-PMH harvesting that our metadata colleagues set up for 
> us, but I’m not sure. I don’t understand what we’re doing wrong to 
> make SO MANY of them show up in the PDFs, which we use as finding aids 
> for patrons or donors that are less tech savvy.  Is there a way to 
> make it so long lists of previous ARKs *do not* show up in the PDF 
> exports?  It would be ideal to not have all the superseded ARKs 
> listed, since the people we are printing these things out for don’t 
> need them and won’t understand what they are.
>
> FWIW, we’re using version 3.3.2, and I haven’t tried to see if this is 
> happening in the sandbox because I’m not actually sure what is causing 
> the ARKs to get superseded in the first place.
>
> Thanks,
>
> Jane
>
> */** Jane Metters LaBarbara *
>
> Head of Archives & Manuscripts, West Virginia & Regional History 
> Center <https://wvrhc.lib.wvu.edu/>
> West Virginia University Libraries
> (304) 293-0352 office
> jane.labarbara at mail.wvu.edu <mailto:jane.labarbara at mail.wvu.edu>
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20230929/a0697d5c/attachment.html>