[Archivesspace_Users_Group] Persistence of ref ids?

[Chris Fitzpatrick]

Hi,

I just updated the API documentation, so it's down while github rebuilds the pages..should be back shortly.

b,chris.


Chris Fitzpatrick | Developer, ArchivesSpace
Skype: chrisfitzpat  | Phone: 918.236.6048
http://archivesspace.org/


________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Prom, Christopher John <prom at illinois.edu>
Sent: Tuesday, December 15, 2015 6:00 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Persistence of ref ids?

I have been assuming these are stable; one way to check would be to see if what function is producing it and what the input value is; it looks like a hash value, but it is unclear to me what input value is being used and what function generates them, or whether it might be called more than one time in response to particular events (although I would hope not!)  I guess one could trace this through the code, unfortunately the API documentation linked here appears to be broken, so I couldn’t check that  . . . . http://archivesspace.org/technicaldocumentation
[http://www.archivesspace.org/sites/default/files/ArchivesSpace%20Logo5.png]<http://archivesspace.org/technicaldocumentation>

Technical Documentation | ArchivesSpace Home<http://archivesspace.org/technicaldocumentation>
archivesspace.org
Built for archives by archivists, ArchivesSpace is the open source archives information management application for managing and providing web access to archives ...


As to the ‘product owner’s group, I’d be interested to hear more about this.    My main exposure to the product owner concept is through agile/scrum methodology, where it has a very defined purpose and is always one person.  There is a decent overview here http://www.romanpichler.com/blog/one-page-product-owner/ and at the links, which I think is a reasonable summary of the role, although there are variations depending on which ‘flavor’ of agile/scrum is used.   Typically, it requires a person with a very specific skill set if it is to be properly executed with strong project management, UX, and customer/stakeholder relations skills and it is a full time staff position.  Most scrum/agile books warn assume it is a single person or even warn against trying to make it a group, although sometimes a ‘product owner group' can take on defined task or work in advisory capacity to the product owner.

But, I am not sure that the project is using using the term in the agile sense---or d some other way???

Chris Prom
University of Illinois




On Dec 15, 2015, at 10:13 AM, Callahan, Maureen <maureen.callahan at YALE.EDU<mailto:maureen.callahan at YALE.EDU>> wrote:

At Yale, we’ve also stored ArchivesSpace ref_ids in our Hydra repository for the same purpose.

I know that there’s some talk of a “product owners” group for ArchivesSpace — I think that it would be good for this kind of group to put together a “data charter” (there’s gotta be a better term) that lays out a minimum set of expectations for ArchivesSpace users -- what elements of the application (and the data therein) are and are not subject to change over time. This would help us make integration plans with more confidence.

Maureen

On Dec 15, 2015, at 10:52 AM, Noah Huffman <noah.huffman at duke.edu<mailto:noah.huffman at duke.edu>> wrote:

Patrick,

We’ve made a couple of decisions internally that assume these ref_ids are persistent.  For example, we’re storing these IDs in our Hydra repository as the primary way to link from digital objects to their description in ASpace.  So, naturally, I’m curious about this too.

-Noah

================
Noah Huffman
Archivist for Metadata, Systems, and Digital Records
David M. Rubenstein Rare Book & Manuscript Library
Duke University | 919-660-5982
http://library.duke.edu/rubenstein/<https://urldefense.proofpoint.com/v2/url?u=http-3A__library.duke.edu_rubenstein_&d=AwMFAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=tX7szkz05Wkf4oLmjcMx2Ev3S-DA0p2JJgXQCtbDasc&s=6GOsMTousP-QKC4CsQG-ALmP7QsFNmtHFsMdch3flhk&e=>



From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>[mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Galligan, Patrick
Sent: Monday, December 14, 2015 2:28 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] Persistence of ref ids?

We’re curious to hear from the devs or anyone with a lot of experience about whether ref_ids in the system ever change their values. I know they don’t upon transfer, and they’re not editable from the user interface, so we’re fairly certain they are permanent and persistent, but want to make sure before making a couple decisions internally.

Can anyone confirm their persistence/permanence?

Patrick Galligan
Rockefeller Archive Center
Assistant Digital Archivist
914-366-6386

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=AwICAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=tX7szkz05Wkf4oLmjcMx2Ev3S-DA0p2JJgXQCtbDasc&s=IeiOQkudgTdOROPNXnFqm-564YvC6zsDTD0UndCsZxE&e=

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto: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/20151215/38e62d48/attachment.html>