Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

metadata fields with <input-type>name</input-type>: field visibility switch is not shown in edit / submission form #47

Open
saschaszott opened this issue Aug 9, 2023 · 0 comments
Labels

Comments

@saschaszott
Copy link

This bug affects DS CRIS 2023.01

The metadata field value visibility switch, e.g. image, is not shown if the metadata field's input type is set to name in submission-forms.xml.

Example

In this example we consider the metadata field crisrp. preferredName in entity type Person.

excerpt from submission-forms.xml

    <form name="person">
      <row>
        <field>
          <dc-schema>crisrp</dc-schema>
          <dc-element>preferredName</dc-element>
          <repeatable>false</repeatable>
          <label>Preferred Name</label>
          <input-type>name</input-type>  <!-- if you change this value to "onebox" it works as expected -->
          <hint />
        </field>
      </row>
      …
    </form>

excerpt from local.cfg

metadatavalue.visibility.Person.crisrp.preferredName.settings = [0 2]

expected behaviour

The edit / submission form shows a visibility switch image next to the input field.

current behaviour

The visibility switch is not shown in the edit/form next to the input field.

image

@saschaszott saschaszott added the bug label Aug 9, 2023
@saschaszott saschaszott changed the title metadata fields with <input-type>name</input-type>: field visibility switch is not shown metadata fields with <input-type>name</input-type>: field visibility switch is not shown in edit / submission form Aug 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant