Bug #4436

Rework how EAD imports/exports creation dates

Added by Mike Cantelon over 9 years ago. Updated about 9 years ago.

Status:VerifiedStart date:12/14/2012
Priority:HighDue date:
Assignee:José Raddaoui Marín% Done:

100%

Category:EAD
Target version:Release 1.4.0
Google Code Legacy ID: Tested version:
Sponsored:No Requires documentation:

Description

Currently uses multiple date elements which isn't compatible with DTD. Used normalized date range in "NORMAL" attribute of date element.

FOO-ISAD-description.PNG - Example of new fonds, FOO, created in ISAD template with dates of creation (36.8 KB) Dan Gillean, 12/17/2012 03:11 PM

FOO-export-EAD.PNG - Screenshot of FOO when EAD export is selected - note that dates of creation are not present in export (69.8 KB) Dan Gillean, 12/17/2012 03:11 PM

FOO-import-roundtrip-error.PNG - FOO when re-imported back into AtoM - dates have disappeared (37.3 KB) Dan Gillean, 12/17/2012 03:11 PM

Date_roundtrip_error_StartEnd_import.png - use case 1: user enters specific start and end dates within a single year (13.3 KB) Dan Gillean, 03/11/2013 04:48 PM

Date_roundtrip_error_StartEnd_import2.png - Use case 2: user enters generic year start date and specific end date (14.2 KB) Dan Gillean, 03/11/2013 04:48 PM

Date_roundtrip_error_StartEnd_import3.png - Use case 3: user enters a single year date (start and end) (12.8 KB) Dan Gillean, 03/11/2013 04:48 PM

Date_roundtrip_error_StartEnd_import4.png - Use case 4: user enters only years for start and end dates (start and end autopopulate) (13.9 KB) Dan Gillean, 03/11/2013 04:48 PM

Radda-fonds-before-Export.png - What my test description looked like in AtoM before export (40.2 KB) Dan Gillean, 04/01/2013 04:51 PM

Radda-fonds-EAD-Export.png - The EAD export from the test fonds (30 KB) Dan Gillean, 04/01/2013 04:51 PM

Radda-fonds-after-Import.png - Test description in AtoM after roundtrip (note duplication of dates) (47.9 KB) Dan Gillean, 04/01/2013 04:51 PM

Radda-fonds-roundtripped-Export-again.png - What happens if you export the roundtripped test fonds again (EAD) (42.2 KB) Dan Gillean, 04/01/2013 04:52 PM


Related issues

Related to Access to Memory (AtoM) - Bug #4845: Import EAD - Warning libxml error - Syntax of value for a... In progress 03/26/2013

History

#1 Updated by Mike Cantelon over 9 years ago

  • Status changed from New to QA/Review
  • Assignee changed from Mike Cantelon to Jessica Bushey

#2 Updated by Mike Cantelon over 9 years ago

  • % Done changed from 0 to 100

Applied in changeset atom|commit:a7b6dc1ef4de0e85291e8599a65e5525126c8670.

#3 Updated by Jesús García Crespo over 9 years ago

  • Target version set to Release 1.4.0

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

  • Category set to EAD

#5 Updated by Dan Gillean over 9 years ago

Dates of creation have disappeared entirely on export in this revision - see attached screenshots:

#6 Updated by Jessica Bushey about 9 years ago

  • Assignee changed from Jessica Bushey to José Raddaoui Marín
  • Priority changed from Medium to High

#7 Updated by José Raddaoui Marín about 9 years ago

  • Status changed from Feedback to QA/Review

Applied in changeset atom|commit:1d753fe2c4286cc54ce8db6b6daf765d7e525ef1.

#8 Updated by Dan Gillean about 9 years ago

Dates are being captured now, and on export, everything looks good.

However, the mapping to the appropriate fields is not working when re-imported. Free-text date field roundtrips perfectly, but the start and end date fields (which are necessary for searching) are not populating correctly, if at all.

One important convention which must be included: if a date is entered simply as the year (ex: 2010), it must not be assumed to be January 1, 2010, (i.e. 2010-1-1). Instead, it should import as 2010-00-00.

This does not seem to be the case in AtoM currently, which if not fixed will become more noticeable in 2.0, when the faceted date range search is introduced, as it will return inaccurate results. For example, currently a date is entered as a single year (i.e. 2010), when reimported, will have both its start and end dates read: 2010-1-1. Meaning if a user searched for 2010-02-01 to 2010-04-01, the search will return false.

I've attached annotated screenshots of several different examples of the problems encountered with dates when roundtripping. I have included information on the user data entered, and the EAD XML exported, on a screenshot of the Edit screen for the dates. "Date_roundtrip_error_StartEnd_import3.PNG" corresponds to the use case example above.

#9 Updated by Anonymous about 9 years ago

  • Status changed from Feedback to QA/Review

#10 Updated by Jesús García Crespo about 9 years ago

  • Status changed from QA/Review to Feedback

#11 Updated by Jesús García Crespo about 9 years ago

  • Status changed from Feedback to QA/Review

Applied in changeset atom|commit:5e10f95248a3d6e340f285023a17efb11b957170.

#12 Updated by Dan Gillean about 9 years ago

Unfortunately, this issue is now causing duplication in the dates fields. Please see the attached screenshots for more information - seems to have to do with interpreting both the <unitdate> in the <did>, and the <chronitem><date type='creation'> as information to add to the events dates in AtoM.

So far, the other issues discussed above appear to be resolved however - could successfully roundtrip both display dates, and custom start and end dates using the YYYY-MM-DD format.

#13 Updated by Dan Gillean about 9 years ago

  • Status changed from Feedback to Verified

Issue with date duplication has been associated with behaviour reported in [https://projects.artefactual.com/issues/4845 issue 4845]. Date formatting on roundtrip associated with this issue has been verified; issue has been closed.

Also available in: Atom PDF