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

Values not visible for hierarchy import #4595

Closed
matthias-ronge opened this issue Aug 18, 2021 · 2 comments · Fixed by #5026
Closed

Values not visible for hierarchy import #4595

matthias-ronge opened this issue Aug 18, 2021 · 2 comments · Fixed by #5026
Labels

Comments

@matthias-ronge
Copy link
Collaborator

matthias-ronge commented Aug 18, 2021

When importing a volume, and the import automatically imports the superior multi-volume work as well, the metadata fields of the multi-volume work are not visible and cannot be edited in the import mask.

Goal: Show and allow to edit metadata from all hierarchically imported records.

Screenshot

@andre-hohmann
Copy link
Collaborator

I understand the problem and because of this missing feature, i take the following approach:

  1. Import the Metadata of the "Multivolume"
  2. Check and modify the metadata of the "Multivolume" and create the process
  3. Import the Metadata of the "Volume"
  4. Check and modify the metadata of the "Volume" and create the process
  5. ...

This approach also avoids the explanation of the import levels, which are difficult to explain - at least for me...
It is necessary to check, if a process for "Multivolume" exists, but it is better then to "repair" its metadata after its import. Very often, all volumes of a multivolume work are processed at once, so that the additional effort is moderate.

Maybe this helps until the feature is available.

@matthias-ronge
Copy link
Collaborator Author

The user interface for creating processes is currently being fundamentally revised in #4322. The conception of this adaptation should be paused until the mentioned revisions have been incorporated. Perhaps they will then be obsolete, or the user guidance could have fundamentally changed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
2 participants