Status: New
Owner: [email protected]
Labels: Type-Defect Priority-Medium
New issue 1966 by [email protected]: Importing EAD <container> element
merges physical location information when name is identical
http://code.google.com/p/qubit-toolkit/issues/detail?id=1966
To reproduce this error:
========================
1)Add physical storage information to a record - e.g. name B-7, type Box
2)Import an EAD file with the same name but different type, e.g. <container
type="Map_Cabinet">B-7</container> - see attached sample
Resulting error:
================
Imported record has physical storage information name: B-7, type: Box; this
container is now linked to both descriptive records
Expected result:
================
A new container should be created, with (in this example) type Map_Cabinet.
More generally, it is not clear how best to handle import of <container>.
There could legitimately be containers with identical name, location and
type which are in fact different containers - e.g. boxes, depending on the
numbering system. The data entry interface allows for this. These
containers should be unique within a particular collection. On the other
hand, shelves and map cabinets (for example) could be unique across an
institution... which gets into the issue of records from different
repositories.
Attachments:
SSUA-150-test.xml 4.0 KB
--
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.
