Feature #5977

Add "Date" field to "Add new child levels" fields

Added by José Raddaoui Marín over 8 years ago. Updated over 7 years ago.

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

100%

Category:Information object
Target version:Release 2.1.0
Google Code Legacy ID: Tested version:
Sponsored:Yes Requires documentation:

Description

Screenshot of the area in question attached for reference.

In the ISAD template, this is in the Identity Area

Add to all templates where this option exists. It will be a single free text date field, but like the existing free-text date fields in the Dates of creation area, when values are added, AtoM will try to parse the dates and add values for Start and End. If the user wants to review and/or change this parsing, they will have to navigate to the new description and edit it via the Dates area - no need to add Start/End fields to the "Add new child levels" section.

test2.png (15.9 KB) Dan Gillean, 11/15/2013 10:19 AM

test3.png (11.7 KB) Dan Gillean, 11/15/2013 10:19 AM

History

#1 Updated by José Raddaoui Marín over 8 years ago

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

AtoM|commit: b28d76791d81cc786d3f386b05c4b90623930004

#2 Updated by Dan Gillean over 8 years ago

Hi Radda,

When multiple child records are added at once, it seems that the dates from the first are being passed down to all additional child records, even if different values are entered.

to reproduce
1) Enter edit mode on an existing archival description
2) Create new child-level descriptions using the quick-entry "Add new child levels" interface:

  • TEST1 - Item - This is test item one - 1984 - [2012?]
  • TEST2 - Series - This is test series two - 2012
  • TEST3 - Subseries - This is test subseries three - [1984?] - 1999

resulting error
All three records end up with 1984 in start date, and 2012 in end date fields. See attached screenshots from edit mode.

Expected result
Dates entered in each new child-level record are respected and preserved.

#3 Updated by Dan Gillean over 8 years ago

  • Status changed from Feedback to Verified

My bad. After further testing, this was a result of browser caching. Clearing the browser cache and re-testing produced the expected results. Marking verified.

#4 Updated by Dan Gillean over 8 years ago

  • Target version changed from Release 2.0.1 to Release 2.1.0

#5 Updated by Dan Gillean over 7 years ago

  • Category set to Information object

#6 Updated by Dan Gillean over 7 years ago

  • Sponsored changed from No to Yes

Also available in: Atom PDF