Comment #3 on issue 1924 by [email protected]: Allow update of existing
descriptions via EAD
http://code.google.com/p/qubit-toolkit/issues/detail?id=1924
I agree that a title can be problematic, and a primary key from the
originating system would be ideal - my questions are:
1) Does EAD have a logical place to put the key?
2) What do we do if the system generating the EAD files doesn't follow our
convention for tracking the key?
3) How do we prevent conflicts with keys from different origin systems
(append repository code, UUID, etc?)
In general, I think unique identifiers are going to be more important for
archival description as the information is moved around, but it does
introduce the extra complication of introducing UUIDs into the originating
system to preserve the relationship.
--
You received this message because you are subscribed to the Google Groups "Qubit
Toolkit Issues" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/qubit-issues?hl=en.
