sers Group
Subject: Re: [Archivesspace_Users_Group] Component unique identifiers
John’s message reminded me that at Duke, our repository items have
externally-minted and persistent ARKs. When we created digital object records
in ASpace based on our repository objects using the service I
org>
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
On Behalf Of Rees, John (NIH/NLM) [E]
Sent: Tuesday, November 6, 2018 10:59 AM
To: Archivesspace Users Group
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Component unique identifiers
Subject: Re: [Archivesspace_Users_Group] Component unique identifiers
Wow, this is super helpful.
We’ve been noodling on a similar use case. All our existing repository projects
leverage our MARC 035 field ids (Voyager ILS-supplied) to mint ids/Fedora PIDs,
but now we’re embarking on ASpace
National Library of Medicine
301-827-4510
From: Rachel Aileen Searcy
Sent: Tuesday, November 06, 2018 9:38 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Component unique identifiers
Hi Adrienne,
We had a similar issue here at NYU. Previous digitization projects relied
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
On Behalf Of Rachel
Aileen Searcy
Sent: Tuesday, November 6, 2018 9:38 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Component unique identifiers
Hi Adrienne,
We had a similar issue here at NYU. Previous digitization projects re
Hi Adrienne,
We had a similar issue here at NYU. Previous digitization projects relied
on the shorter Archivist's Toolkit refids for file naming, but this became
untenable with those created by ArchivesSpace. We didn't want to change our
inter-departmental workflows too radically, so we
Hi Adrienne,
We ran into a similar issue at Boston College when we migrated from to
ASpace from Toolkit. Our practice had been to combine the collection ID
with an auto-generated refID to create component unique identifiers, but
the auto-generated refIDs in Aspace were much too long for our
Thanks for bringing this up, Adrienne!
Would you (and others) be willing to share your perspective on the following
tickets?
https://archivesspace.atlassian.net/browse/ANW-770
https://archivesspace.atlassian.net/browse/ANW-780
I think it would be helpful to hear about the diverse approaches to
of Cory
Nimer
Sent: Friday, September 21, 2018 4:00 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Component Unique Identifiers questions
Linda,
We are still working on our PUI implementation locally, but I believe it should
be possible to set your ArchivesSpace
PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Component Unique Identifiers questions
Maggie-
This is what I see when looking at a finding aid in the public interface after
having selected a particular item from the pull down "Collection Organization"
l
Hi all,
Just FYI, here is my drafted JIRA ticket. I didn’t mention anything about
changing the placement of the CUI in the data entry of the staff interface.
Please feel free to comment on the ticket, in case I missed or misinterpreted
anything!
yralists.lyrasis.org
on behalf of Hughes,
Margaret
Sent: Thursday, September 20, 2018 12:54 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Component Unique Identifiers questions
Larry—Thank you for sharing how you’re (not) working with the CUI. Regarding
the
Group
Subject: RE: [Archivesspace_Users_Group] Component Unique Identifiers questions
Larry—Thank you for sharing how you’re (not) working with the CUI. Regarding
the other ASpace example for the field, accession number, we also track that
information via linked accessions or an Immediate Source
Subject: Re: [Archivesspace_Users_Group] Component Unique Identifiers questions
Thank you all for bringing up this topic. At Purdue (we are using version 2.2.1
at the moment), we do use the CUI to help distinguish the intellectual
arrangement; this has proven very helpful in search results
rme...@purdue.edu>
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of
Larry Weimer
Sent: Thursday, September 20, 2018 10:16 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Com
Maggie,
To answer your first question, we (New-York Historical) do not currently
use the CUI field at all. We include "Series X" or "Subseries X.1" in the
component title. The other ASpace example for this field, accession number,
we would include in an Immediate Source of Acquisition note
60-567-4501
lhock...@litchfieldhistoricalsociety.org
eboardman.tumblr.com
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Tang,
Lydia
Sent: Thursday, September 20, 2018 9:24 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group
Hi Maggie,
Thanks for following up with my questions, I'm glad we're having this
discussion because I think we could create a JIRA ticket about this issue if we
(as the membership) would like to see this area potentially altered/clarified.
I personally would support having the CUI default to a
Confusion over the CUI field came up recently for us, as well, and we're
wondering how we should move forward using it.
Regarding the first question: I'm wondering if other institutions are using the
CUI to record information like "Series I" or "Subseries 8.4"? And if so, are
you happy with
Group <archivesspace_users_group@lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Component Unique Identifiers
Good day Linda, Steve, and all,
My archives has also been working with the Component Unique Identifier (CUI)
following a migration from Archon. At Purdue, we have
, 2018 9:40 AM
To: Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Component Unique Identifiers
Steve,
A belated thank you for this reply. We do not have on site support for database
issues, but I sent it to our consult
If I understand what you want correctly:
Copy public/app/views/shared/_idbadge.html.erb into
plugins/local/public/views/shared/
( assuming local plugins are enabled ) and add a line to display
result.identifier, for example:
$ diff -U 6 public/app/views/shared/_idbadge.html.erb
22 matches
Mail list logo
