Need revision number to uniquely specify docid
The xml_documents.docid field is currently used to store the metadata identifier
for all xml documents. However, our revision system creates new versions of the
document each time a UPDATE or DELETE is performed on the document.
Consequently, we need a "revision number" field in the "xml_revisions" table in
order to differentiate the various revisions. We also need a way of specifying
the revision number in the various xml formats used to pass the metadata
identifier, such as the meta_file_id fields, and in the eml-package
Finally, this has implications for the use of the docid in uniquely specifying a
document before and after it has been revised.
Old version NCEAS:1 --
New version NCEAS:1 NCEAS:1/1
So, in fact, when werefor to the old version as NCEAS:1 in a document, and then
later revise it and refer the the revision as NCEAS:1, we are generating
#2 Updated by Chad Berkley over 19 years ago
The revision number for each document is tracked through the xml_documents and
xml_revisions tables. A specific revision of a document can be returned by
specifying the revision number as the last number in the accession number. If
the revision number is omitted, the newest document is retrieved. for example:
NCEAS.1.5 is the newest revision of a document. If I want to view the previous
revision I can request document NCEAS.1.4. If I want the newest document I can
request NCEAS.1 or NCEAS.1.newest.
When a query is performed the complete accession number including the revision
is always returned.