-
Notifications
You must be signed in to change notification settings - Fork 63
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
Implementation of seasons does not work porperly #3637
Comments
Test #3740 shows that this basically works. We can safely remove the blocking label, I think. |
@matthias-ronge: Can you confirm that you can still create processes for seasons? If so, could you tell me the Kitodo version you apply? In case you need information, here is a summary of what i do and the result of it.
Result:
Thus, the seasons are applied in ORDERLABEL, but the processes are not assigned to the correct year-process. |
I don’t use that feature, so I can’t tell right away. Needs testing, but sounds like a bug. I reopen this issue |
@matthias-ronge : Thanks a lot! |
May be related to #4824 |
@matthias-ronge : Thanks for the hint it leads to issue Maybe the correction of that issue leads to the loss of functionality to create seasons correctly. Unfortunately, i cannot find out, how the problem in #4363 was solved. Can you confirm, that the seasons cannot be created correctly? Just to make sure that the reason is our configuration. |
@andre-hohmann Are you aware of #3741? Cite: <division id="Season">
<label>season</label>
<subdivisionByDate yearBegin="--07-01">
… In addition, a button for setting the start of the year exists in the calendar editor. → The beginning of the year must be entered exactly equal to the setting in the rule set, or processes with the wrong substructure are created. |
@matthias-ronge : No, i wasn't. But that seems to be the solution - thanks a lot! I added the "documentation" label to #3741 and close the comment. |
Problem
For seasons, it is necessary, that the process of issues are assigned to the year-element according to the beginning of the season. This is not January, but usually August or September.
If the beginning of the season is defined as 01.09. the ORDERLABEL is generated formally correctly, as for example:
Thus, it seems as if seasons are recognized generally.
The allocation of the issues to the year is not working properly, as it works according to newspaper issues, for example:
All issues should be assigned to 1850/1851
Solution
Seasons must be depicted correctly in the METS-files.
Examples
Examples 3.x
Click to show the exported METS-File:
Click to show the exported METS-File:
Examples 2.x
The text was updated successfully, but these errors were encountered: