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

Error in pagination #4700

Open
stefanCCS opened this issue Sep 24, 2021 · 11 comments
Open

Error in pagination #4700

stefanCCS opened this issue Sep 24, 2021 · 11 comments

Comments

@stefanCCS
Copy link
Collaborator

Release 3.3.1
I have found an issue in pagination: For the first page the pagination value is not stored in meta.xml.
In meta data editor you can see it correctly:
grafik
In meta.xml ist looks like this (after saving):
grafik

@stefanCCS
Copy link
Collaborator Author

Some more tests have shown, that this issue might onyl occur in combination with "extended structure" meta data view.

@stefanCCS
Copy link
Collaborator Author

@solth : Try to check this Release 3.5.0-beta.
It looks like that the "extended structure" does not exists anymore (at least I cannot find anymore the checkmark in the workflow editor).
Can you confirm this?
image

@BartChris
Copy link
Collaborator

It still exists, red switch at top of workflow editor
grafik

@stefanCCS
Copy link
Collaborator Author

fyi:
I do not use "Extended Structure" anymore. Therefore, this issue has low to zero priority for myself.

@stefanCCS
Copy link
Collaborator Author

@solth : Feel free to close this issue, or keep it open - as you wish ...

@solth
Copy link
Member

solth commented Mar 13, 2023

@stefanCCS thanks for the comments. There are several features of the editor that are not really incoporated into the extended view, yet, so I will keep this issue open until we have feature parity between combined and extended tree.

@stefanCCS
Copy link
Collaborator Author

@solth : Question is, if "Extended View" is a feature, which is used at all. Maybe a discussion could be opened on the "Community email list"? (If it is not really used, I simply would discontinue this feature (declare this as "deprecated")).
So, what do you think ? (or any other opinion?)

@solth
Copy link
Member

solth commented Mar 13, 2023

@stefanCCS the extended structure tree is a central feature used in the Swiss Federal Archive and therefore cannot be deprecated.

@stefanCCS
Copy link
Collaborator Author

@solth
ok, understood.
But still, if they are the only Power-User, we could ask and understand, what parts of this feature they use.
(e.g. it looks like they do not bother about this issue here).
If you think this is reasonable, I can discuss this also in the next Board-Meeting (with your participation, if you like).
So, again, what do you think?

@solth
Copy link
Member

solth commented Mar 13, 2023

As I said I think we should not remove a feature that is actively used. This issue should remain open because it is not solved, yet, but can be considered low priority.

@stefanCCS
Copy link
Collaborator Author

@solth
ok, understood.
But still, if they are the only Power-User, we could ask and understand, what parts of this feature they use.
(e.g. it looks like they do not bother about this issue here).
If you think this is reasonable, I can discuss this also in the next Board-Meeting (with your participation, if you like).
So, again, what do you think?
(main idea from my side is, to avoid maintaining features, which are not really used ...)

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

4 participants