Editor / Add list mode

[fxprunayre]

The list can be used to display a list of contact with only organisation name for example. This can facilitate building simple form hiding the details of ISO elements. In this case, use a contact directory to add new contact makes sense.

This mode can be also more efficient when record contains lots of contacts which in some case can create large HTML form which can take time to build, download and render in the browser (eg. when having more than 100 contacts in a record). If only label are used the form will be faster to render.

For large XML record, form may trigger error like Form with too many keys [1001 > 1000] when submitted. The list mode allows to deal with such situation.

eg.

<action type="add"
        forceLabel="true"
        addDirective="data-gn-directory-entry-selector"
        or="pointOfContact"
        in="/gmd:MD_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification">
  <directiveAttributes
          data-template-add-action="false"
          data-search-action="true"
          data-popup-action="true"
          data-template-type="contact"
          data-variables="gmd:role/gmd:CI_RoleCode/@codeListValue~{role}"/>
</action>

<list name="Contact point"
      xpath="/gmd:MD_Metadata/gmd:identificationInfo/*/gmd:pointOfContact[*/gmd:role/*/@codeListValue = 'pointOfContact']"
      del="."
      sortBy="gmd:organisationName/gco:CharacterString">
  <item href="*[1]/@uuid">
    <label xpath="*/gmd:organisationName/gco:CharacterString/text()"/>
  </item>
</list>

<list name="Originator"
      xpath="/gmd:MD_Metadata/gmd:identificationInfo/*/gmd:pointOfContact[*/gmd:role/*/@codeListValue = 'originator']"
      sortBy="gmd:organisationName/gco:CharacterString">
  <item>
    <field xpath="*/gmd:organisationName"/>
  </item>
</list>

Funded by Ifremer

Checklist

• I have read the contribution guidelines
• Pull request provided for main branch, backports managed with label
• Good housekeeping of code, cleaning up comments, tests, and documentation
• Clean commit history broken into understandable chucks, avoiding big commits with hundreds of files, cautious of reformatting and whitespace changes
• Clean commit messages, longer verbose messages are encouraged
• API Changes are identified in commit messages
• Testing provided for features or enhancements using automatic tests
• User documentation provided for new features or enhancements in manual
• Build documentation provided for development instructions in README.md files
• Library management using pom.xml dependency management. Update build documentation with intended library use and library tutorials or documentation

[josegar74]

What is the difference between text and the other values?

[fxprunayre]

See https://github.com/geonetwork/core-geonetwork/blob/main/schemas/config-editor.xsd#L1447-L1453 so you can also add text in the list item. It is not used for now but for example, we could think of

Org name
<hr/>
Address ...

[josegar74]

Testing this example, the input box for the organisation, can be removed, but then is removed the organisation, not the contact (in the label mode, it is removed the contact, what makes more sense).

It's not something critical, but to confirm this is expected:

[fxprunayre]

Yes, there is no del attribute in list, so the item has no button for removal. The org name is a normal field so can be removed as usual. If using

<field xpath="*/gmd:organisationName" del="ancestor::gmd:pointOfContact"/>

would remove the contact.

For now, we are more thinking using this mode with directory entries and only label.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud