ArchivesSpace ARKs

[Michelle Echols]

Hello,

I am new to ARKs, but our library is hoping to use them through ArchivesSpace to link to our finding aids. Has anyone used ArchivesSpace to generate ARKs? Do we still need to use an ARK managing tool if ArchivesSpace is generating the ARKs? If ArchivesSpace generates the keys, do we still need to come up with opaque prefixes?

Thank you for any help!

Michelle

[Greg Janée]

This webinar may be of interest: https://archivesspace.org/archives/5930
-Greg

> --
> You received this message because you are subscribed to the Google Groups "ARKs" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to arks-forum+...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/arks-forum/841dd578-8e81-4be2-a911-115ec04db544%40googlegroups.com.

[Seth Shaw]

I would start by watching the webinar Greg included. (Side note: at least in my email the link didn't work because it appended Greg's signature to it; be sure when you go to the URL it ends with the 5930). 

We have not started minting ARKs with ArchivesSpace; although the webinar discusses ArchivesSpace's capabilities for supporting it. 

Although ArchivesSpace can generate it's own ARK identifiers, it uses your PUI for the URL prefix. If, instead, you wanted to use a different resolver (such as http://n2t.net/) you would need some workflow for creating the ARK in one system and updating the other. For example, we at UNLV will probably continue minting finding aid ARKs using the EZID API and updating our Resource records' "external ARK" field via the API.

I'm not sure what you mean by the "opaque prefixes". The identifiers are usually opaque, but not the prefixes. The ARK URL prefix is the resolver (e.g. "http://n2t.net/" or "http://aspacepui.example.org/"), then you have the rest of the ARK: the ARK prefix "ark:/", then the NAAN (assigned by the CDL), then a (usually opaque) identifier. Either ArchivesSpace (for internal ARKs) or some other service (for external ARKs) will be responsible for creating the (ideally) opaque identifiers.  

To view this discussion on the web visit https://groups.google.com/d/msgid/arks-forum/874C9F33-19DF-4106-A051-C9BBF98A7D44%40ucsb.edu.

[Michelle Echols]

Thank you, Greg! I didn't know about this webinar and it was very helpful!

On Wednesday, April 29, 2020 at 5:08:59 PM UTC-4, Greg Janée wrote:

This webinar may be of interest: https://archivesspace.org/archives/5930
-Greg

> On Apr 29, 2020, at 1:36 PM, Michelle Echols <michell...@mail.wvu.edu> wrote:
>
> Hello,
>
> I am new to ARKs, but our library is hoping to use them through ArchivesSpace to link to our finding aids. Has anyone used ArchivesSpace to generate ARKs? Do we still need to use an ARK managing tool if ArchivesSpace is generating the ARKs? If ArchivesSpace generates the keys, do we still need to come up with opaque prefixes?
>
> Thank you for any help!
>
> Michelle
>
> --
> You received this message because you are subscribed to the Google Groups "ARKs" group.

> To unsubscribe from this group and stop receiving emails from it, send an email to arks-...@googlegroups.com.

[Michelle Echols]

Thank you Seth! We had some confusion around what the webinar called "shoulders" (letters at the beginning of the ARK identifier). The webinar and your explanation at the end of your post helped me clear things up.

Thanks again!

On Wednesday, April 29, 2020 at 11:55:41 PM UTC-4, Seth Shaw wrote:

I would start by watching the webinar Greg included. (Side note: at least in my email the link didn't work because it appended Greg's signature to it; be sure when you go to the URL it ends with the 5930). 

We have not started minting ARKs with ArchivesSpace; although the webinar discusses ArchivesSpace's capabilities for supporting it. 

Although ArchivesSpace can generate it's own ARK identifiers, it uses your PUI for the URL prefix. If, instead, you wanted to use a different resolver (such as http://n2t.net/) you would need some workflow for creating the ARK in one system and updating the other. For example, we at UNLV will probably continue minting finding aid ARKs using the EZID API and updating our Resource records' "external ARK" field via the API.

I'm not sure what you mean by the "opaque prefixes". The identifiers are usually opaque, but not the prefixes. The ARK URL prefix is the resolver (e.g. "http://n2t.net/" or "http://aspacepui.example.org/"), then you have the rest of the ARK: the ARK prefix "ark:/", then the NAAN (assigned by the CDL), then a (usually opaque) identifier. Either ArchivesSpace (for internal ARKs) or some other service (for external ARKs) will be responsible for creating the (ideally) opaque identifiers.  

On Wed, Apr 29, 2020 at 2:08 PM Greg Janée <gja...@ucsb.edu> wrote:

This webinar may be of interest: https://archivesspace.org/archives/5930
-Greg

> On Apr 29, 2020, at 1:36 PM, Michelle Echols <michell...@mail.wvu.edu> wrote:
>
> Hello,
>
> I am new to ARKs, but our library is hoping to use them through ArchivesSpace to link to our finding aids. Has anyone used ArchivesSpace to generate ARKs? Do we still need to use an ARK managing tool if ArchivesSpace is generating the ARKs? If ArchivesSpace generates the keys, do we still need to come up with opaque prefixes?
>
> Thank you for any help!
>
> Michelle
>
> --
> You received this message because you are subscribed to the Google Groups "ARKs" group.

> To unsubscribe from this group and stop receiving emails from it, send an email to arks-...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/arks-forum/841dd578-8e81-4be2-a911-115ec04db544%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "ARKs" group.

To unsubscribe from this group and stop receiving emails from it, send an email to arks-...@googlegroups.com.