Task #1578
Feature #1577: use tables for storing System Metadata in Metacat
refactor metacat tables
100%
Description
potentially merge xml_documents, xml_revisions, identifiers, and systemmetadata if it make sense
History
#1 Updated by Ben Leinfelder over 13 years ago
instead of merging all the tables I would go for this approach (comments welcome):
-keep 'xml_documents' and 'xml_revisions' as they are (using docid+rev)
-use 'identifier' table as the only mapping point for connecting guid with docid+rev
-remove 'docid' and 'rev' columns from the 'systemMetadata' table
-all operations that require guid would first look up the guid from 'identifier' if needed (say if we needed system metadata but only had the docid+rev)
-all operations that require docid would first look it up via 'identifier' using the guid it has (looking up access control rules from xml_access table, for example)
#2 Updated by Ben Leinfelder over 13 years ago
- Status changed from New to In Progress
removed the docid and rev columns from systemMetadata and any mapping methods that might have tried to use those columns.
#3 Updated by Ben Leinfelder over 13 years ago
- Status changed from In Progress to Closed
actually, I think this is the extend of the changes I'll make to existing tables.
there are other tasks to create tables for storing other system metadata facets
