Ticket #1841 (closed enhancement: fixed)
timestamp issues
| Reported by: | cjg@… | Owned by: | cjg |
|---|---|---|---|
| Priority: | Intend to | Milestone: | EPrints 3.0 RC 1 |
| Component: | Data Model | Version: | 2.3.13 |
| Severity: | normal | Keywords: | |
| Cc: |
Description (last modified by cjg) (diff)
The single datestamp should be replaced with 2 timestamp fields:
- First approved (datestamp)
- Last modified (lastmod)
Creation time or first-submitted is also possible, but I can't see a use for it.
The $eprint->datestamp() method will need to be reviewed to only be called when then item first enters the "archive" table.
This slightly changes the meaning of the "datestamp" field. Old records will list their "deposited" time as the last time it entered the archive.
Items not in the buffer and inbox will have their datestamp set to NULL. Items in the live archive and deletion will have it left alone.
The value of lastmod will be take from datestamp before the NULLS are set on buffer and inbox.
Features using "datestamp" will need to use one of the two fields. All will need to be reviewed.
- bin/import_eprints
- cgi/oai2
- cgi/latest_tool
- cgi/users/staff/buffer
- cgi/users/home
- cgi/latest
- cgi/soap/soap
- User.pm
- RSS.pm
- Subscription.pm
- OpenArchives?.pm
- EPrint.pm
