...
- Should changes to CollectionObject entities be versioned?
ATS: Yes, for the purpose of maintaining an audit trail.
AUDIT TRAILS
- What type of audit information do we need to keep track of for CollectionObjects?
- Audit trail for creating, reading, updating, deleting, etc?
- Audit trail for domain specific work flows or schema extensions?
ATS: Yes, audit trails for create, read, update, delete, etc.: It would be terrific to offer an audit or versioning option for domain specific work flows or schema extensions. As I recall there was a discussion thread about this that included the idea of a 'snapshot in time' idea wherein one could go back in time to see what a record looked like. Dan showed a sample of a project that he worked on that included this type of feature. I would very much like to see us offer this functionality. Whether it belongs in the next 6 mos work plan or not, I am not able to say given that I do not fully understand the effort involved to do this. I see this as different from audit. And, therefore, a separate deliverable. If they are one and the same in terms of effort to develop, let's discuss further about where to schedule this effort in.
PARTS AND SUB-OBJECTS
- Do we need to model parts and/or subobjects? If so, are parts and sub-objects considered full-fleged collection objects?
ATS: Yes, we do need to model parts and sub-objects. They are two different concepts in museum work. Yes, they can be considered full-fledged collectionobjects. They may be treated, travel, be displayed, photographed separately, so may participate in any procedure.