We're updating the issue view to help you get more done. 

Metadata elements administration: Type restrictions not displayed anymore

Description

After adding/removing type restrictions of one metadata element several times, not all assigned type restrictions are displayed anymore.

I've attached screenshots:

  • fail1: Shows that "record source" element is associated with object types "Work, Variant, Manifestation"

  • fail2: Shows that only "Work" is displayed as type restriction. Variant and Manifestation are assigned, but not displayed anymore.

I already deleted and re-created this metadata element, because before that no type restrictions at all were displayed anymore

Happy to help debugging this!

Environment

None

Activity

Show:
Peter Bubestinger
April 4, 2018, 8:03 AM

I've marked this as "Blocker", because it is not possible to add this field to some object types anymore - or edit to reflect the correct behavior.

User known
April 4, 2018, 8:53 AM

Yes, I noticed this the other day. It's inadvertently filtering restrictions with a specific type set when displaying. This commit resolves the issue: https://github.com/collectiveaccess/providence/commit/aa6bc246416e81d6b8353b27d634b699acaff60d#diff-9c73a42432093110f92c807080dd17d6

Peter Bubestinger
April 4, 2018, 11:33 AM

Does that mean if I apply the changes of that commit to "app/models/ca_metadata_elements.php", the type restrictions will be visible again, or does the patch only avoid this issue from happening in the first place?

Ready and willing to test your patch and report back

User known
April 4, 2018, 11:37 AM

The restrictions are all there. This will allow them to be listed. It'll fix everything in other words
You might have to clear the application cache after adding this

The patch is in v1.7.6 which will be released in ~ a week or maybe in 2020 at the rate things are going.

Assignee

User known

Reporter

Peter Bubestinger

Labels

None

Components

Affects versions

Priority

Blocker
Configure