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

Unnecessary OPAC search in creation of processes for periodical volumes #3966

Closed
andre-hohmann opened this issue Aug 21, 2020 · 8 comments
Closed

Comments

@andre-hohmann
Copy link
Collaborator

Problem

When a process for a periodical volume is created by the +-Symbol in the process list, the OPAC-import is shown. This is not necessary, because the metadata cannot be imported from the union catalog.

Solution

It would be better, if the Tab "Title record link" is shown.

Examples

periodical01

periodical02

periodical03

@solth
Copy link
Member

solth commented Aug 24, 2020

There can be constellations where metadata for child processes can be imported indvidually via a search interface - we actually have such a case with an OAI-PMH interface right now. So I don't think we should generally not show the import dialog when creating subprocesses.
Perhaps this should be configurable via kitodo_opac.xml or ruleset?

@andre-hohmann
Copy link
Collaborator Author

Which document types are imported via the OAI-PMH? Is it also periodical volumes?
Will it occur often? It will be still possible to open the search with the button "Catalogue search". I know that processes for periodical volumes will be created very often.

If it should be configured, it should in my opinion be configured in the ruleset, too. Otherwise, it gets complicated. Maybe two attributes are needed:

  1. use="createChildrenFromParentWithOPACSearch"
  2. use="createChildrenFromParentWithoutOPACSearch"

@solth
Copy link
Member

solth commented Aug 24, 2020

In the described case it will probably occur regularly. The problem with configuring it via the ruleset is that than it doesn't depend on the search interface for the import anymore. It should depend on the interface, though, because only the interface defines what features are supported during import.

@andre-hohmann
Copy link
Collaborator Author

If it is necessary, the configuration can also be implemented in the kitodo_opac.xml. I have to admit that i have no idea how to realize it.

@solth
Copy link
Member

solth commented Aug 24, 2020

You are probably right that the default case should be not to open the import dialog when creating a child process. Then the configuration only needs to be added for the exception when some child processes are indeed to be imported from a search interface. I guess we should propose that improvement in a separate issue.

@matthias-ronge
Copy link
Collaborator

I don't understand what the second ticket is for. It's all about that one question, isn't it? Did you just create a duplicate or did I not understand something correctly?

@matthias-ronge
Copy link
Collaborator

Related: #3561, #3407

@andre-hohmann
Copy link
Collaborator Author

You are right, i should have closed this issue.

The issue #3970 focuses on the ability to configure the import for children processes in the kitodo_opac.xml :

  1. with OPAC search
  2. without OPAC search ("Title record link")

In this issue, the demand of replacing of the OPAC-search for children processes was straightforward. I did not know that this feature is needed in other use cases. Enable the configuration, everyone can use it according to the demands. Otherwise , i expect suggestions for improvement like this in the future.

As the issue #3970 is more flexible and sustainable, i close this issue.

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

No branches or pull requests

3 participants