Task #3748 (new)
Opened 9 years ago
Last modified 7 years ago
Record Modified Dates
| Reported by: | ajpatterson | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | Unscheduled |
| Component: | Specification | Version: | n.a. |
| Keywords: | schema | Cc: | |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
Moved from http://www.ome-xml.org/ticket/83
- In anticipation of a more comprehensive and automated versioning system, I would like to suggest that we at least record:
- Dates changes have been made to the record
- Who made the changes
- Optionally, a text-based description of the changes.
- Dates changes have been made to the record
- For the most part, this can still be automated, with text describing the changes available for the die-hard. (There are many library and museum metadata standards that use this kind of by-hand notation.)
Changed by andrew
Metadata - top level date last changed? Floating element that could be put anywhere?
Changed by andrew
Also free text field for reason.
Change History (4)
comment:1 Changed 8 years ago by ajpatterson
- Keywords schema added
comment:2 Changed 8 years ago by mlinkert
comment:3 Changed 7 years ago by ajpatterson
- Component changed from Model to Specification
- Owner set to ajpatterson
comment:4 Changed 7 years ago by ajpatterson
- Owner ajpatterson deleted
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Comment from Jason Palmer (library science student at LOCI):
PREMIS ("PREservation Metadata: Implementation Strategies") is a Library of Congress-sanctioned standard that—as the name suggests—is used for preservation and archiving. However, its ability to add events to the history of the file as well as linking the events to a specific user would be useful.See also PREMIS web site: http://www.loc.gov/standards/premis/index.html