Bug #8296

DACS specialized notes are not being saved

Added by José Raddaoui Marín about 7 years ago. Updated almost 7 years ago.

Status:VerifiedStart date:04/17/2015
Priority:MediumDue date:
Assignee:Dan Gillean% Done:

0%

Category:DACS
Target version:Release 2.2.0
Google Code Legacy ID: Tested version:2.2
Sponsored:No Requires documentation:

Description

When an archival description is created/edited using the DACS template, the specialized notes are not saved.

dacs-special-notes.png - Special notes types in DACS (15.8 KB) Dan Gillean, 04/23/2015 01:23 PM

dacs-edit-template.png - DACS edit template after adding special notes in RAD and switching templates (71 KB) Dan Gillean, 04/23/2015 01:45 PM

rad-view-template.png - RAD view template after adding special notes (132 KB) Dan Gillean, 04/23/2015 01:45 PM

Related issues

Related to Access to Memory (AtoM) - Bug #6003: DACS Technical access field doesn't roundtrip (EAD export... New 11/20/2013
Related to Access to Memory (AtoM) - Bug #8355: RAD and DACS specialized notes do not crosswalk, and swit... New 04/29/2015

History

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

  • Related to Bug #6003: DACS Technical access field doesn't roundtrip (EAD export/import) added

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

  • Status changed from New to QA/Review
  • Assignee changed from José Raddaoui Marín to Dan Gillean

#3 Updated by Dan Gillean about 7 years ago

Testing
  • Create a new description using the DACS template
  • Add special notes - see attached screenshot
  • Export as EAD
Error encountered
  • None of the notes are in the EAD export
Expected result
  • DACS EAD export includes all the special notes.
Another issue
  • DACS special notes do not crosswalk to RAD special notes where there is crossover.

For example, the following should be true

  • DACS alphanumeric designations note = RAD alphanumeric designations note
  • DACS Conservation note = RAD Conservation note
  • DACS Variant title information = RAD Variations in title
Additionally:
  • Create a description in RAD
  • Add all of the RAD special notes types - title notes and special notes
  • Add data to the Control area fields as well. Save the record
  • Switch the default template to DACS, and enter edit mode.
Resulting error:
  • Although the view page looks fine (except for specialized notes from RAD that could crosswalk not showing up), in the edit template, a whole bunch of data appears in the specialized notes boxes that shouldn't - compare the two attached screenshots, rad-view-template.png and dacs-edit-template.png
Expected result
  • Specialized notes that can crosswalk (listed above) should display in the correct fields, with the correct drop-downs set, in the DACS view and edit templates
  • Notes that do not crosswalk from RAD should not appear in the edit template of DACS. This is the design pattern we have followed with all the other templates, and it should hold true here.

#4 Updated by Dan Gillean about 7 years ago

  • Related to Bug #8355: RAD and DACS specialized notes do not crosswalk, and switching templates with specialized notes causes errors in the edit template added

#5 Updated by Dan Gillean about 7 years ago

It turns out that the second problem described in the notes above, the crosswalking between RAD and DACS, is much more complicated than getting the DACS notes into the EAD export. To keep the focus on the original issue and allow us to resolve it without getting drawn into the broader challenges of crosswalking, I have created a new ticket for the crosswalking issue (#8355) and have related it to this one. We can deal with it there when we have time and a plan.

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

  • Status changed from Feedback to QA/Review
  • Assignee changed from José Raddaoui Marín to Dan Gillean

Fixed the DACS specialized notes population in the edit template and add those notes to EAD export.

#7 Updated by Dan Gillean about 7 years ago

  • Status changed from QA/Review to Feedback

So, I'm not sure if this should go here or on a different ticket...

The DACS notes are definitely appearing in the EAD now:

<odd type="conservation">
  <p>DACS conservation note</p>
</odd>
<odd type="citation">
  <p>DACS citation note</p>
</odd>
<odd type="variantTitleInformation">
  <p>DACS variant title information note</p>
</odd>
<odd type="processingInformation">
  <p>DACS Processing information note</p>
</odd>

However, since they have not been added to the import script, they will not re-import.

Radda, let me know if you think this should go on a new ticket.

#8 Updated by Dan Gillean almost 7 years ago

  • Assignee changed from Dan Gillean to José Raddaoui Marín

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

  • Status changed from Feedback to Code Review
  • Assignee changed from José Raddaoui Marín to Mike Gale

PR 180

#10 Updated by Mike Gale almost 7 years ago

  • Assignee changed from Mike Gale to José Raddaoui Marín

looks good

#11 Updated by José Raddaoui Marín almost 7 years ago

  • Status changed from Code Review to QA/Review
  • Assignee changed from José Raddaoui Marín to Dan Gillean

#12 Updated by Dan Gillean almost 7 years ago

Looks good.

FYI for anyone following this thread:

It turns out that these terms are not in the same taxonomy as the RAD special notes terms, which makes crosswalking them more difficult. For now, we have implemented a separate EAD profile for DACS specialized notes on import and export, like so:

 <odd type="dacsConservation">
      <p>Conservation note DACS</p>
    </odd>
    <odd type="dacsCitation">
      <p>Citation note DACS</p>
    </odd>
    <odd type="dacsAlphanumericDesignation">
      <p>Alphanumeric designations note DACS</p>
    </odd>
    <odd type="dacsVariantTitleInformation">
      <p>Variant title information note DACS </p>
    </odd>
    <odd type="dacsProcessingInformation">
      <p>Processing information note DACS</p>
    </odd>

#13 Updated by Dan Gillean almost 7 years ago

  • Status changed from QA/Review to Verified

Also available in: Atom PDF