You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The problem that only one result is displayed in the Title Record Link tab has been identified in the pull request:
This might lead to corrections in the metadata editor or on other stages of the workflow.
It would be better, if all relevant processes are shown in the Title Record Link tab, to enable corrections.
Describe the solution you'd like
It should be possible to find several results in the Title Record Link tab, which should also been displayed.
Example: Show all processes with the same base-ID and not a random one:
PrivZitob_1860391834
PrivZitob_1860391834-17860000
PrivZitob_1860391834-17870000
A possible technical solution might be described in:
Thank you for creating the additional issue @andre-hohmann, but it has to be noted that the issue is only present in the Pull Request #5869, not in the current master branch.
The link for the possible solution (#5869 (comment)) is pointing to a solution for a different issue (the search in tite Title Link Tab is not a search for parents, but a general search, this is now adressed in #5967).
The problem that the search is not displaying mutiple results is adressed here: #5869 (comment)
Is your feature request related to a problem? Please describe.
The problem that only one result is displayed in the Title Record Link tab has been identified in the pull request:
This might lead to corrections in the metadata editor or on other stages of the workflow.
It would be better, if all relevant processes are shown in the Title Record Link tab, to enable corrections.
Describe the solution you'd like
It should be possible to find several results in the Title Record Link tab, which should also been displayed.
Example: Show all processes with the same base-ID and not a random one:
A possible technical solution might be described in:
The text was updated successfully, but these errors were encountered: