Hi Kate,
Nope, I do mean containers and not components. Container @id and @parent attributes are randomly generated on export, which is why the are different on each export.
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 Bowers, Kate A. <kate_bowers at harvard.edu>
Sent: Monday, January 26, 2015 5:03 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] container ids in exported EAD changing
Can we clarify-do you mean *component* Ids?
Kate
Kate Bowers
Collections Services Archivist for Metadata, Systems, and Standards
Harvard University Archives
kate_bowers at harvard.edu<mailto:megan_sniffin-marinoff at harvard.edu>
617.496.2713
voice: (617) 384-7787
fax: (617) 495-8011
web: http://nrs.harvard.edu/urn-3:hul.eresource:archives
Twitter: @k8_bowers
From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chris Fitzpatrick
Sent: Monday, January 26, 2015 4:29 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] container ids in exported EAD changing
Hi Steven,
Yes, the id is randomly generated since there is a need to have the ability to associated containers to their possible children ( by way of a @id and @parent_id ). The problem is that when creating the container node, currently it's not known if a child container is on the way, so the @id has to be made just in case.
Is it a large blocker for you?
b,chris.
Chris Fitzpatrick | Developer, ArchivesSpace
Skype: chrisfitzpat | Phone: 918.236.6048
http://archivesspace.org/
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Steven Majewski <sdm7g at virginia.edu<mailto:sdm7g at virginia.edu>>
Sent: Friday, January 23, 2015 9:04 PM
To: Archivesspace Users Group
Subject: [Archivesspace_Users_Group] container ids in exported EAD changing
I was just doing some tests on exporting EAD ( AS v1.1.1 ) and I noticed
that the container ids change on every export:
<c02 id="aspace_ce99c6434158423922d1cb7269d2d6eb" level="file">
<did>
<unittitle>William Faulkner Foundation</unittitle>
<unitdate type="inclusive">1961-1978, undated</unitdate>
<container id="aspace_a8d7a56421f7fe676aece03cb158231c" label="Text" type="Box-folder"
>6:10</container>
</did>
</c02>
<c02 id="aspace_ce99c6434158423922d1cb7269d2d6eb" level="file">
<did>
<unittitle>William Faulkner Foundation</unittitle>
<unitdate type="inclusive">1961-1978, undated</unitdate>
<container id="aspace_7786fd082905fc4e886fccda4539c9b6" label="Text" type="Box-folder"
>6:10</container>
</did>
</c02>
Is there a reason for this ?
I see that the c02/@id stays the same and is the value of the archival_object's ref_id ( with "aspace_" prefix added ).
If the container ids are not stored in ArchivesSpace and are generated differently on the fly for export,
it would be better to just not add an id attribute.
- Steve Majewski
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20150127/56389c5a/attachment.html>