www/pool.psychoinformatics.de-ui
10
0
Fork 0
Code Issues 10 Pull requests Activity Actions

Do not recommend existing identifiers #20

New issue
Open
opened 2025-12-19 14:33:58 +00:00 by msz · 2 comments
msz commented 2025-12-19 14:33:58 +00:00
Member
Copy link

When adding identifiers to a Person record, I am presented with a list of other Persons' identifiers already present in the system:

scr5

Considering that identifiers are usually specific to a person, I think this is cluttering rather than helpful.

When adding identifiers to a Person record, I am presented with a list of other Persons' identifiers already present in the system: ![scr5](/attachments/743adc4e-3841-4545-84b9-955451d38b3c) Considering that identifiers are usually specific to a person, I think this is cluttering rather than helpful.
scr5.webp
10 KiB
👍 2
mih commented 2026-01-16 08:14:17 +00:00
Owner
Copy link

This requires a configuration similar to id_iri that enables shacl-vue to know what an identifier (of this kind) really is. Because in principle, most of what it does is presenting identifiers for reuse. And this issue is asking for not doing what it is built for.

This requires a configuration similar to `id_iri` that enables shacl-vue to know what an identifier (of this kind) really is. Because in principle, most of what it does is presenting identifiers for reuse. And this issue is asking for not doing what it is built for.
jsheunis commented 2026-02-25 10:46:13 +00:00
Member
Copy link

It is technically possible to restrict the types of records to show in the dropdown (InstancesSelectEditor) by using show/hide config specific to the component and class:

component_config:
  InstancesSelectEditor:
    dcterms:Identifier:
      show_classes: []
      show_classes_with_prefix:
      hide_classes: []
      hide_classes_with_prefix:
        - xyzri
        - dlthings

That should hide everything inside the dropdown.

But I'm leaning towards @mih's interpretation. This would be working around what the intended use of the InstancesSelectEditor is: presenting records of a specific class (and subclasses) for selection. An example where hiding the items would not be useful is if the identifier that the user wants to link has already been created, then the user would not know this.

It is technically possible to restrict the *types* of records to show in the dropdown (`InstancesSelectEditor`) by using show/hide config specific to the component and class: ```yaml component_config: InstancesSelectEditor: dcterms:Identifier: show_classes: [] show_classes_with_prefix: hide_classes: [] hide_classes_with_prefix: - xyzri - dlthings ``` That should hide everything inside the dropdown. But I'm leaning towards @mih's interpretation. This would be working around what the intended use of the `InstancesSelectEditor` is: presenting records of a specific class (and subclasses) for selection. An example where hiding the items would not be useful is if the identifier that the user wants to link has already been created, then the user would not know this.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels   
AI
No labels
AI
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
www/pool.psychoinformatics.de-ui#20
No description provided.