[Archivesspace_Users_Group] RFC: Should a revision statement be produced on import?

[Majewski, Steven Dennis (sdm7g)]

We have to do significant preprocessing of our EAD to get them to import into ArchivesSpace, so I append a revisiondesc/change item in my pre-import stylesheet. But I wouldn’t object to additional tagging, as my change item is dated from when the stylesheet is run and not the AS import. It would be useful if it added the ArchivesSpace version and importer. So far, we’re usually using import plugins for EAD — in 1.4.2 a modified version of Yale plugin to get barcodes imported, in 1.5.1 test, a different plugin to import dao|daoloc/@role —> digital-object.use_statement and fix some other problems. So it would be handy to track those details as well (and that is not info available to the pre-processor stylesheet, so that would be value added for me).

ArchivesSpace export adds a <creation> element with date: I guess it makes sense to tag it there rather than revision stmt, since from ASpace POV, it is a new EAD creation & serialization, even if we are using it as a replacement for an existing EAD. ( i.e. from MY POV, its a revision. ) ASpace version and serializer info would be useful here as well. 


— Steve Majewski



> On Sep 19, 2016, at 12:04 PM, Mayo, Dave <dave_mayo at harvard.edu> wrote:
> 
> Hello all,
> 
> Locally at Harvard, there's a desire to have a revision statement be added to records when imported into ArchivesSpace from EAD.  Our rationale is that import into ArchivesSpace from other systems/formats is a significant event in the lifetime of the record, and that it's appropriate to track it in record content as well as in the creation time of the db record.
> 
> If there's general approval of the idea, I can package up our code so it can be added to ArchivesSpace proper, and make it available as a plugin. 
> 
> Currently, we plan to add a revision statement reading "Imported into ArchivesSpace" or "Imported into ArchivesSpace via conversion from ${converter_type}." 
> 
> The Github issue discussing this is here: https://github.com/archivesspace/archivesspace/issues/527
> 
> - Dave Mayo
>   Digital Library Software Engineer
>   Harvard University > HUIT > Library Technology Services
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group