If you load a manifest, or import canvases from an existing manifest, the image dimensions appear to be blank.

To reproduce:
Click "Load manifest" and enter http://digi.vatlib.it/iiif/MSS_Vat.lat.3773/manifest.json.
Check canvas dimensions in the Canvas Metadata section.

Dimensions do appear if you add an image onto a canvas via changing the image URI. Should these be non-editable?

Tried both demos in chromium and firefox and they don't seem to work, tried building it myself and even that doesn't work, anybody else experience the same?

I get this in the console:

Uncaught TypeError: Cannot read property '@id' of undefined
    at t.getInitialState (bundle.js:41)
    at new t (bundle.js:31)
    at I._constructComponentWithoutOwner (bundle.js:31)
    at I._constructComponent (bundle.js:31)
    at I.mountComponent (bundle.js:31)
    at Object.mountComponent (bundle.js:12)
    at I.performInitialMount (bundle.js:31)
    at I.mountComponent (bundle.js:31)
    at Object.mountComponent (bundle.js:12)
    at T.mountChildren (bundle.js:31)

Check all manifest level metadata fields in the spec and the ones that only accept certain valid values should be changed from free text to drop-down with valid values.

Example:
The drop-down menu should have the following options:

• left-to-right
• right-to-left
• top-to-bottom
• bottom-to-top

I've read the README and user manual but I find it's missing one detail: whether this product can be used to produce and edit IIIF manifests to a level of detail similar to that of the structMap in METS.

For an example of what I mean, please see the TOC in a volume like https://gutenberg.beic.it/webclient/DeliveryManager?pid=2386355

If a user creates a new manifest with the tool, the "add canvas" button makes it clear that the thumbnail slider is editable. However, when editing an existing manifest--the use case I envision most frequently for documentary editors--it's not at all apparent that anything beyond canvas metadata is editable.

Perhaps a splash screen would help new users, or an info button with pop-over help?

If you're dragging a canvas from an external manifest, the dotted line around the canvas in the thumbnail strip (where the imported canvas will go) doesn't appear unless you have already rearranged some of the canvases in the thumbnail strip.

The public folder should be regenerated to incorporate the latest changes.

I can do this and create a new tag release, if appropriate.

Potential users of the application should be aware that they can use the instance at
iiif.bodleian.ox.ac.uk/manifest-editor/
without necessarily having to complete a local installation.

It would be helpful if the modal metadata windows in the canvas importer showed the custom metadata as well as the predefined fields.

after command npm run buildI get an error message
"ERROR in ./app/app.jsx
Module not found: Error: Cannot resolve module 'leaflet/dist/leaflet.css' in /Users/nastasia/iiif-manifest-editor/app
@ ./app/app.jsx 31:0-35

I followed all steps in ReadMe

Trying to open this manifest for editing will fail with an error:
http://dams.llgc.org.uk/iiif/4574752/manifest.json

This is due to it containing multilingual labels. This needs to be supported. See also issue #24

The site myjson.com is set as default when creating a new manifest at https://digital.bodleian.ox.ac.uk/manifest-editor .

However, it seems to be down for some time.

Does anyone know a replacement store?

I think the problem here is that the editor doesn't recover well from failing to load a manifest. Here are the steps I took to reproduce the error:

1. Loaded this manifest into the editor: https://iiif.lib.harvard.edu/manifests/drs:48309543

2. Opened the canvas importer and loaded these manifests:
   https://iiif.lib.harvard.edu/manifests/drs:5981093
   http://dams.llgc.org.uk/iiif/4574752/manifest.json

3. Received a "error: invalid remote manifest URL" message when loading the last manifest. The same message appeared again when I tried to load the first manifest I had loaded (https://iiif.lib.harvard.edu/manifests/drs:48309543). When I closed the message, I couldn't close any of the manifests, open the information windows, add canvases, or return to the edit manifest view; I could only rearrange and edit the canvases that were already in my main manifest thumbnail sequence.

Bug report by Emma:
"at the moment, when I loaded a right-to-left viewing direction, the thumbnail order changed, but then it changed back (and continued to change back and forth) every time I clicked on a different thumbnail. (You can see this quite easily with this two-canvas manifest: http://iiif.bodleian.ox.ac.uk/iiif/manifest/51372634-f77b-4840-93c3-d8972d906413.json.)"

The main viewer and the image displayed are not centered correctly on initial page load. It is off by about 25% to the right. When resizing the window or closing and re-opening the metadata sidebar, the viewer is centered correctly.

Hi,
I've been trying to add an image to a new manifest via the tool and I keep getting a "URI is not valid" error.
I've tried it as an image (level0):
https://philippinestudies.uk/mapping/images/iiif/manila-panel1/full/full/0/default.jpg

And as an info.json file:
https://philippinestudies.uk/mapping/images/iiif/manila-panel1/info.json
http://free.iiifhosting.com/iiif/94ed082cc0af882a704b6cac380dde873d1830157d383e1a02bb089adf16999e/info.json

Yet it works as a level1 image:
https://free.iiifhosting.com/iiif/94ed082cc0af882a704b6cac380dde873d1830157d383e1a02bb089adf16999e/full/full/0/default.jpg

Manifest here:
https://philippinestudies.uk/mapping/iiif-manifests/manila-panel1/manifest.json

I was wondering what was wrong with the info.json files above and what's wrong with the level0 image.

Can you let me know?

Thanks!

When storing the manifest remotely using a defined endpoint, the name of the manifest is automatically generated. Is there any way I can assign the name?

Help text could be something like:
"Please note that this will actually reverse the order of the canvases in the sequence for this manifest. If you just want to change the viewing direction please use the viewing direction toggle button in the Sequence Metadata panel."

Hi,
I am writing on behalf of the Silk Museum. We have been using https://digital.bodleian.ox.ac.uk for creating manifests of the photo collection. Unfortunately we have been receiving an error recently, is this a temporary thing or should we be searching for other ways to create/edit manifestos?

The canvases do get added to the target manifest sequence as can be verified when returning to "Edit Manifest" view. The thumbnail strip in the "Import Canvases" view does not update however, giving no visual feedback to the user.

This bug must have been introduced with the viewingDirection feature that let's you reverse the display of the canvases.

Editing the canvas dimensions causes the new dimensions to be saved in the manifest as strings, rather than integers.

Link to the user manual from the landing page, as well as from the edit interface and maybe the import canvases view

Drag & drop a IIIF Icon from e-codices or Digital Bodleian on the "Open Manifest" drag area => nothing happens. Same for drag & drop in "Import Canvases"

Should this go into the Sequence panel?
Should toggling this option update the viewingDirection property in the manifest (most likely yes)?

When running Firefox on an Ubuntu VirtualBox, text boxes resize too aggressively, becoming less than the height of the text in the box.

If you try to load or import canvases from an invalid manifest, you won't be able to load a valid manifest either until you clear your browser cache. It would be good if the editor were a bit more resilient in these cases.

To reproduce this error:

1. Go to iiif.bodleian.ox.ac.uk/manifest-editor/.
2. Choose "New manifest".
3. Go to "Import canvases".
4. Load this manifest: http://www.qdl.qa/en/iiif/81055/vdc_100000000241.0x0003bd/manifest
5. After closing the error message, try to load this manifest: http://iiif.bodleian.ox.ac.uk/iiif/manifest/beeedb51-90cd-4119-84fb-c7e9ffb0b214.json. You should see the same error message.
6. Try again after clearing the browser cache.

In Safari, the thumbnail sequence appears extremely small.

When you add a new field, the default text for both label and value is "N/A".
Replace "N/A" with "Label" and "Value".

In Chrome, the thumbnail panel in OpenSeadragon disappears when you move your mouse to scroll forward or backward in the sequence. This means that scrolling can only be done with arrow keys.

To reproduce:

• open a new manifest
• go to Import Canvases
• import a sequence
• try to scroll forward through the thumbnails of your imported sequence

NB this doesn't happen in Firefox.

Actually, uploading any manifest seems to not work.

Steps to reproduce...

Start manifest editor and select "open manifest"
Select upload from computer and browse to a file
Get error "Error loading local manifest. Please select valid..."
Browser console reveals:

XHR PUT https://iiif-manifest-editor.textandbytes.com/manifestUpload

Status 405 Method Not Allowed
Version HTTP/2
Transferred 1.15 kB (933 B size)
Referrer Policy strict-origin-when-cross-origin
Request Priority Highest

Hi @schwemmer,

@calvinbutcher has had a pull request accepted to the IIIF validator, so it should now accept POST requests. Please could the manifest editor utilise this rather than GET via a 3rd party.

IIIF/presentation-validator#25

Note: route for POST is actually just /validate, not /postvalidate.

Thanks,
Chris

In Chrome 84 on MacOS if I start a new manifest and click Add Canvas I get a broken image icon on the Empty canvas with a spinning loading symbol.

Sidebar changes from "This sequence does not have any canvases." to "The selected canvas has been deleted."

See http://dmt.bodleian.ox.ac.uk/manifest-editor/ on this repo homepage

When you duplicate a canvas and then change the image URI for the duplicate, it also changes the image URI for the original canvas. You can change all the other metadata independently, however, and it would be good to be able to change the image URI independently as well, as it would make it a bit easier to add new images.

Uploaded manifests are stored under uploads/manifests with a UUID as file name. This directory never gets cleared and fills up over time. It would probably make sense to clear the uploads on start up as the files are not being reused.

The save button generates a manifest for you to download.
Another option would be to supply a callback so one can upload
this manifest wherever you want. This way this UI can be used
as an editor for an admin interface.

Or is this just intended as an application that edits and exports manifests?

Editor doesn't recognize these manifests as valid (even ones that were just made and validated a minute ago with the editor).

I would like to add a small Python server to this project, since it will fit in better with our deployments at the Bodleian.

Is the purpose of the Express server.js just to serve out the public directory? Is there anything else I should keep in mind when creating this?

Instead of copying the collection to a JSON file hosted on the server, have a file with a list of top-level collection URIs. This way we can easily add new collections, and existing collections will be up-to-date. I don't know how significantly this will affect load time. Possibly the fetched collections could be cached locally for a set time, if fetching them anew each time slows things down a lot.

Adding an empty canvas and then painting on an image URI results in a "manifest base API is not set" error when validating the manifest.

node-sass is giving a lot of problems when installing the IIIF manifest editor locally, especially when switching node environments (e.g. when testing different node versions with nvm) and when on Windows. node-sass then usually needs to be recompiled. The error messages are cryptic and not helpful. Also, the Sass project has switched to Dart, see here: https://sass-lang.com/blog/announcing-dart-sass

To reproduce:

1. Load http://iiif.bodleian.ox.ac.uk/iiif/manifest/9c7e4a6e-ab08-4372-a0be-d914d8cfd7f2.json into editor.
2. Copy the image URI from the second canvas in the sequence.
3. Change the image URI for the first canvas in the sequence to an invalid URI. An error message will appear.
4. Replace the invalid URI with the URI copied from the other canvas. Don't click away from the canvas you're editing. The new image will load, but the error message will persist until you click away to a different canvas and then click back.