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

Newspaper-issues: two logical structure trees #3418

Closed
andre-hohmann opened this issue Apr 8, 2020 · 4 comments
Closed

Newspaper-issues: two logical structure trees #3418

andre-hohmann opened this issue Apr 8, 2020 · 4 comments

Comments

@andre-hohmann
Copy link
Collaborator

andre-hohmann commented Apr 8, 2020

Problem

In processes of newspaper-issues, there are two structure trees. One consists of two elements "Unknown structure type".

Example "logical and a structure tree":

doublestructuretree01

The export of these processes is aborted with the following message in the task manager:

  • crashed (metadata validation failed)

Example "one structure tree"

doublestructuretree02

Export progress 0%:
errorexport01

Questions

  • Does this have to be?
  • Are there other issues regarding this phenomenon?
@andre-hohmann andre-hohmann changed the title Newspaper-issues: two logical structure tree Newspaper-issues: two logical structure trees Apr 11, 2020
@matthias-ronge
Copy link
Collaborator

Displaying the structure trees of all superordinate processes is a feature at the moment. It has to be shown whether the practice proves it.

The “export is 0%” looks like a bug to me, but has nothing to do with the other. @andre-hohmann, could you please create a separate ticket for the second one?

@andre-hohmann
Copy link
Collaborator Author

The "export-problem" cannot be described in one ticket. There are severel problems, as for example:

From my point of view, the issue can be closed. If it causes problems, we can open a new one - hopefully with more information.

@matthias-ronge
Copy link
Collaborator

So then, this ticket should only deal with this problem: Export says "finished" but progress is 0%. Goal: Either, if an error has occurred, it should not be "finished", but the error must be displayed (with text that reports what the error is). If no error occurred, 100% should be reached.

@andre-hohmann
Copy link
Collaborator Author

I opened a new issue for it, with a correct name: #3440.

Thus, i will close this issue.

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

No branches or pull requests

2 participants