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
manifest order #943
manifest order #943
Conversation
… the data setting to an empty array so tests succeed
Neat. |
👍 for tests! |
Hi, I have just been exploring the "preserveManifestOrder" option and it does not seem to be working in the current version. I just wanted to check if it was supposed to be working yet? |
Hmm, I will take a look @jpadfield |
You are right, something is not working correctly. I reopened #570. If you have any more info, please add it to that ticket. |
OK, Thanks, I do not have any specific new information but I will add Joe On 18/10/16 09:36, Rashmi Singhal wrote:
Joseph Padfield |
closes #570
Added
preserveManifestOrder
setting to determine whether or not to display the manifests in a particular order. By default, Mirador does the original behavior - displaying items in the manifest page as they resolve, becausepreserveManifestOrder
is set tofalse
. If set totrue
the code attempts to determine the index value for that manifest and insert it properly according to the other manifests that have already been added to that page. If the index value for a manifest is not available for some reason (i.e. added by URL or the URI in thedata
array does not match the URI in the manifest itself), default to adding them to the top, as Mirador typically adds them.