Yes, so we do create our own ‘persistent identifiers’ from the country code, repository code and reference. We don’t use one that is within a description - otherwise we’d have a motley selection of identifiers, and anyway, most descriptions don’t come with any kind of identifier.
You can see on the Hub we’ve just added a ‘cite’ facilitation - so from https://archiveshub.jisc.ac.uk/data/gb986-jenp
you click on ‘Cite’ and we include the full reference as something that they can use in a citation. We also give them the citation for the Hub page itself using our URI.
We also have local sites for HE contributors, and we use the same kind of pattern for those, e.g. for Brunel they have a URI for a description: https://archiveshub.jisc.ac.uk/bruneluniversity/data/gb1975-ctun
If a contributor has an identifier for their description, we would hope that would be in the description, usually as a link in the ‘additional finding aids’ field, so that we use it to link to their website. However, we can also attempt to deal with ‘alternative identifiers’, such as with the British Library: https://archiveshub.jisc.ac.uk/data/gb58-addms89010
- so this has the EAD:
<unitid countrycode="GB" encodinganalog="3.1.1" identifier="Add MS 89010" label="current" repositorycode="58">Add MS 89010</unitid>
<unitid identifier="ark:/81055/vdc_100000000094.0x0000c1" label="alternative" type="ark">ark:/81055/vdc_100000000094.0x0000c1</unitid>
We would always encourage contributors to have a link to their own description, at any level of description, but we do get some instances of these going to 404s over time.
> On 6 Sep 2018, at 20:32, Dan Gillean <d...@artefactual.com
> Hi Jane,
> Actually, that's very helpful, but also opens another question.
> Scott, if ArchivesHub is going to ignore any URI anyway in favor of building a new URI based on the identifier /reference code, then do you in fact need the URL in your OAI EAD response to be able to send the data to the Hub? Also wondering if it is simply possible to harvest at the top level, since EAD XML is meant to capture an entire hierarchy, and any individual descriptions post-import in ArchivesHub would not use the same URI as where they originated. Perhaps this is about ArchivesHub being able to point back to source content? Trying to better understand your use case :)
> Additionally, I believe that the DC XML response *should* include digital object paths - you can see an example of this in our documentation, in the second example response for the GetRecord request, here:
> • https://www.accesstomemory.org/docs/latest/user-manual/import-export/oai-pmh/#get-record
> Let me know if you are not seeing this in responses where it is expected, and I can do some testing to see if you've encountered a bug.
> Dan Gillean, MAS, MLIS
> AtoM Program Manager
> Artefactual Systems, Inc.
> To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/CAC1FhZL1kibjJGjTrk_XkAfsqvCHrHRu69_RG08WLiDaanW5sQ%40mail.gmail.com