ArchivesSpace should create revision_statement on import.
Description
Complexity
Activity
Jason LoefflerJune 29, 2017 at 7:22 PM
Our archivists support some manner of configurable event on record creation. Is it possible to include capacity for creating a migration and/or ingestion event at the time records are ingested via the API?
Dave MayoJune 28, 2017 at 12:29 PM
So, we implemented in a plug-in, so I don't really have an institutional impetus driving me anymore, but I think some kind of information should be captured, outside of creation. People often need to make the distinction between imported and directly entered, or source of import (e.g. we have these problems with our EAD records and not our Excel records), etc.
Event seems reasonable to me, and once I'm done with my current side project (which terms in late July), I'd be happy to work up something if I can scare up some desiderata from various archivists.
Mark CusterJune 27, 2017 at 7:38 PM
Just chiming in to say that I agree with Brad about this. I wouldn't consider an import to be a revision to the finding aid. It could be attached as an event, perhaps, but I don't know how useful that is or what else would be expected regarding that event record.
Jason LoefflerJune 27, 2017 at 7:37 PMEdited
The Dev Pri team view is that an import statement does not represent a revision to the finding aid.
Laney McGlohonApril 5, 2017 at 8:42 PM
From ,
I think it would be a good idea to raise this question on the Users Group List, as it may be possible that not everybody will agree that an import is a revision of the finding aid. I would like to see how much community support there might be for this idea. -bdw
Details
Assignee
UnassignedUnassignedReporter
Dave MayoDave MayoPriority
MinorHarvest Time Tracking
Open Harvest Time Tracking
Details
Details
Assignee
Reporter
Dave MayoPriority
Minor
While creation time of the record is captured in the database and thus preserved in ArchivesSpace as a system, it's not captured as an event in the life of the record.
A couple of people (mostly at Harvard, some others) have supported the idea of a revision statement added to represent the import process. As far as I can tell, this could be added in two places:
the individual importers
StreamingImport#do_create) around #L267
It seems to me that it makes sense to put it outside the converter, so that every record gets an import statement regardless, and make the content overridable in config (maybe in converter?)
I'm having to do the work either plugin-wise or otherwise for Harvard anyway, so I'm happy to put up a PR, if people think this is a good idea generally.