Why I cannot toggle on annotations?
fishfree opened this issue · comments
On this page, when I click on the "toggle annotations" icon, no toolbar displays.
Do you want to display it or to remove it? By default, the annotations are useless, they require a backend, so it's better to remove the icon. See the readme for that.
@Daniel-KM I want to add annotations. I tried to add config JSON in the Mirador json config (item)
section, admin/site/s/{mysite}/settings page as below:
{ "mainMenuSettings": { "show": false }, "windowObjects": [ { "loadedManifest": {manifestUri}, "canvasID": {canvasID}, "viewType": "ImageView", "displayLayout": false, "bottomPanel": false, "sidePanel": false, "annotationLayer": true, "canvasControls": { "annotations": true, "imageManipulation": { "manipulationLayer": true } } } ] }
Still no luck with anonymous user or admin user.
So how to make annotation feature working? I know some annotation store server like simpleannotationserver or Harvard catch.
Note that the config should be :
"loadedManifest": __manifestUri__,
"canvasID": __canvasID__,
because __manifestUri__ and __canvasID__ are replaced statically.
But in a future version, it may be possible to use your config, it's cleaner.
For the annotation server, I didn't tried yet, so I don't know.
@Daniel-KM I tried your spelling before posting this issue, no luck. Thank you all the same! :-)
And in the log, there is a message that is added when the json config is not good.
@Daniel-KM Thanks! I followed the tip and now I can annotate. But annotation data can only saved in the browser's local storage. I want to it presistent? How to make that, please?
Edit: I notice you also develop the Omeka-S-module-Annotate module, why cannot just use that module as the Mirador's annotation storage endpoint?
Yes, it's an important improvement to make Annotate an endpoint for annotation. Annotate is only a backend module. A specific module should be written to adapt the front end data to the back end.
In fact, the Open Annotation standard has three parts: Data Model, Vocabulary and Protocol. Only the first is implemented, and it is enough for Omeka. The protocol should be implemented to support any other widget compatible with Open Annotation, but it is an heavy task, unless if a php library can be used (it wasn't the case when the module was created).
So for now, use another endpoint.
@Daniel-KM Thank you for detailed explanation! Could you please tell me more about how to use another endpoint? Do you think this repo & doc can be integrated?
It's not the client part that we need, because Mirador has already one, but the server part. So catcha or hypothesis can be used as server part. For this module, I need a php server endpoint part to integrate it fully.
@Daniel-KM Daniel, I find the SimpleAnnotationServer here, which provides HTTP API endpoints. So would you please integrate it with Omeka-S-module-Mirador to persist user-generated annotations?
For that, some code should be added in mirador as indicated in the mirador-annotations page.
Currently, only the server annotot and the local storage are available. So this is a work to do, but it is a real work.
I don't understand why mirador need a specific connector for each endpoint, because it is the same protocol. So I think that a copy of the Annotot adapter with a different name "StandardAdapter" should be nearly fine. Or even did you try with the AnnototAdapter? Have you a annotation endpoint to check it?
@Daniel-KM Daniel, thank you for your explanation! Sorry I'm not a programmer :-(.
Any update on this issue?