[Archivesspace_Users_Group] container ids in exported EAD changing

[Steven Majewski]

On Jan 26, 2015, at 4:29 AM, Chris Fitzpatrick <Chris.Fitzpatrick at lyrasis.org> wrote:

> 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.
> 

I didn’t think containers had children, either in EAD schema or JSON model — however I’m still learning
how to mentally parse JSON models, so I could be wrong there. 


> Is it a large blocker for you?

Not currently a big problem: I was just trying to use diff to debug some other export issues,
and was surprised to see so many differences between exports.  

We can just strip container/@id out with an XSLT stylesheet. 

I don’t expect it to be a problem in production, as we don’t typically use container/@id in our EAD. 

We were more concerned that it might represent a symptom of some inconsistency in the model. 
( We’re still in the process of upgrading and verifying that the “jumping component” problem is gone. ) 


— Steve. 


> 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 Steven Majewski <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
> 
> 
> _______________________________________________
> Archivesspace_Users_Group mailing list
> 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/20150126/3fd886dc/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4943 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20150126/3fd886dc/attachment.bin>