Bug #5212

EAD <dimensions> element fails to import into AtoM

Added by Dan Gillean almost 9 years ago. Updated almost 9 years ago.

Status:VerifiedStart date:06/10/2013
Priority:MediumDue date:
Assignee:José Raddaoui Marín% Done:

100%

Category:EADEstimated time:7.00 hours
Target version:Release 1.4.0
Google Code Legacy ID: Tested version:
Sponsored:No Requires documentation:

Description

Both <dimensions> and <extent> are contained within the <physdesc> element, and should map to the ISAD element 3.1.5 Extent and medium. Currently however, only <extent> is used. David has suggested adding labels to clarify the relationship between these two elements on import, like so:

EXTENT AND MEDIUM:
monoograph
extent: 72 pages (38 blank)
dimensions: 16,5 × 21,5 cm

To do this will require several small changes in the EAD import script:

1) add support for <dimensions> on EAD import
2) David has suggested that using HTML definition lists can be a way of generating the labels on import. so that needs to be applied, so the two are distinguished.


Related issues

Related to Access to Memory (AtoM) - Bug #5340: Extent field adding text upon EAD import Verified 07/12/2013
Related to Access to Memory (AtoM) - Bug #5867: <physdesc> data dropped during import Verified 10/25/2013
Related to Access to Memory (AtoM) - Bug #6153: multiple nested elements under <physdesc> are not assigne... Verified 12/18/2013
Related to Access to Memory (AtoM) - Bug #7278: Do not convert extent sub-elements to HTML definition lis... Verified 09/19/2014

History

#1 Updated by José Raddaoui Marín almost 9 years ago

  • Status changed from New to QA/Review
  • % Done changed from 0 to 100

Applied in changeset atom|commit:e2466ecd025a1f206bc27cb547b0530ccd613c2c.

#2 Updated by José Raddaoui Marín almost 9 years ago

  • Status changed from QA/Review to In progress
  • % Done changed from 100 to 80

#3 Updated by José Raddaoui Marín almost 9 years ago

  • Status changed from In progress to QA/Review
  • % Done changed from 80 to 100

Applied in changeset atom|commit:04964c4d09aa3cc98c848cdc344fcec3580d61da

#4 Updated by Jesús García Crespo almost 9 years ago

  • Estimated time set to 7.00

#5 Updated by Dan Gillean almost 9 years ago

  • Status changed from QA/Review to Verified

I tried importing a number of different ways ( dimensions with @encodinganalog and without; dimensions with extent present and without, etc.) and had no problems. the <dl> tags show up in the interface if a user edits the doc, but are not visible in the showscreen, and when a user re-exports, the information maps nicely to <extent> and <dimensions> respectively. Nice fix!

#6 Updated by Dan Gillean almost 7 years ago

  • Related to Bug #6153: multiple nested elements under <physdesc> are not assigned to parent definition list label added

#7 Updated by Dan Gillean almost 7 years ago

  • Related to Bug #7278: Do not convert extent sub-elements to HTML definition list on EAD import added

Also available in: Atom PDF