Feature #5971

Add ability to hide "Archival History" field from public view

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:

0%

Category:UsabilityEstimated time:2.00 hours
Target version:Release 2.1.0
Google Code Legacy ID: Tested version:
Sponsored:Yes Requires documentation:

Description

We should implement this via the existing "Visible elements" module, I think.

The field in question:
ISAD: Context Area > Archival history.

RAD: Archival description area > Custodial history.

In DACS the field maps to: Acquisition and Appraisal elements > Custodial history. But we don't currently have a Visible elements module for the DACS template.

History

#1 Updated by Tim Hutchinson over 8 years ago

Hi Radda,

I found the thread where we scoped out the visible elements module:
https://groups.google.com/forum/#!topic/qubit-dev/HKqNe7OClJE

This confirms my recollection that we specifically excluded archival/custodial history since it's considered mandatory at the highest level of description.

In RAD, material acquired directly from the donor is supposed to be recorded in immediate source of acquisition, although it is common to see these elements combined. In ISAD, that's an optional rule. Custodial history should really provide context about the history of the records as opposed to confidential information about a donor. Immediate source of acquisition is already available on the visible elements module.

I can certainly see why the request comes up, but I wanted to provide that background.

#2 Updated by Dan Gillean over 8 years ago

Hi Tim,

Your points are sound, however: this is the public-facing ticket for a feature request being developed for a client, which will become available to all users. The work is being done for the ISAD template, though we will make the option available to the RAD template as well - it will be up to users to determine whether and how they use it.

#3 Updated by Tim Hutchinson over 8 years ago

Thanks Dan, good to know. I was trying to avoid suggesting that the change definitely shouldn't happen; just wanted to fill in the background.

#4 Updated by Tim Hutchinson over 8 years ago

Radda, our developer just pulled down the latest version and we're getting a 500 error on the visible elements module. I'm guessing it's related to your current work on this issue? the stack trace says:
500 | Internal Server Error | InvalidArgumentException
Widget "isad_archival_history" does not exist.

We should be able to work around this for now, but FYI just in case.

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

Hi Tim,

You'll need to run "php symfony tools:upgrade-sql" so the new settings are added to your database.

Sorry for the inconvenience, I forgot to say it here.

#6 Updated by Tim Hutchinson over 8 years ago

Thanks, Radda - I should have thought of that.

#7 Updated by Tim Hutchinson over 8 years ago

That did the trick.

I'm probably jumping the gun since you haven't marked this for review, but I just wanted to suggest that the archival history field be listed first (to reflect the order of the elements in the templates); and as you noted above, in the RAD template the correct label is Custodial history.

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

Thanks Tim, I've made those changes.

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

  • Target version changed from Release 2.0.1 to Release 2.1.0

#10 Updated by Jesús García Crespo over 7 years ago

  • Target version changed from Release 2.1.0 to Release 2.2.0

#12 Updated by Dan Gillean over 7 years ago

  • Status changed from New to Verified
  • Target version changed from Release 2.2.0 to Release 2.1.0

Almost missed this ticket - thanks for pointing out Tim :) - it will be in the 2.1 release!

Also available in: Atom PDF