Image annotations can be added or edited from this page: https://cdli.mpiwg-berlin.mpg.de/artifact-asset-annotations/add. First, upload a file containing annotations (see below for which file formats are supported). Then, confirm that the file was parsed correctly. Afterwards, add metadata to your annotations by describing the work that was done, and adding associated authors and projects.
To annotate images in CDLI, you need to employ an external image annotator. We prefer to use the VGG Image Annotator (VIA) for which the instructions are below.
Load the VIA2 annotator by visiting the following URL: https://www.robots.ox.ac.uk/~vgg/software/via/via.html. You can also open an offline copy of via.html in you browser.
Click "Project" -> "Load" and point the file selector to the following file: https://cdli.mpiwg-berlin.mpg.de/files-up/cdli-via2-template-2024-04.json. This is a VIA2 project JSON file which contains a pre-defined list of names that can be manually annotated. You may want to download this file first in your local computer.
Click "Project" tab on the left side and then click "Add URL" to add an image URL.
Draw a rectangular region by pressing mouse button and dragging it. After the region is defined, you can describe the content of the region by selecting one of the items (e.g. standing figure) from the dropdown menu.
Save a copy of your work as a VIA2 project by clicking "Project" -> "Save". This will save a JSON file that you can use for future reference.
To contribute your annotations to the CDLI project, follow these steps.
To edit existing annotations of an artifact, follow these steps.
JSON imports following the W3C Web Annotation Data Model are supported, but should conform to the following restrictions, as linked data is not yet supported in full:
@context used in the examples of the W3C specification.AnnotationCollection object, an AnnotationPage object, or an array or
object with individual annotations as values. In the case of AnnotationCollection objects, only the
annotations included in the file are imported.target. This target should have a
source consisting of the URL of the CDLI image you are annotating (e.g. /dl/photo/P123456.jpg).
This target should have a single selector of the type SvgSelector. Preferably, use only <polygon>,
<circle>, <ellipse>, and <path>, and do not use attributes like transform.body but may have more. These bodies
should have the type TextualBody or SpecificResource. The bodies may have any or no purpose.
Bodies may additionally have a value and/or a source.license.id (@id) should be the
URL of the existing annotation (https://cdli.mpiwg-berlin.mpg.de/artifact-asset-annotations/123
where 123 is the numeric ID of the annotation).The fields created, modified, and creator are not supported for importing, and instead
are filled in from the update event(s) associated with the annotations.
{
"@context": "http://www.w3.org/ns/anno.jsonld",
"id": "https://cdli.mpiwg-berlin.mpg.de/artifact-asset-annotations/123",
"type": "Annotation",
"body": [
{
"type": "TextualBody",
"value": "crudely inscribed",
"purpose": "commenting"
},
{
"type": "SpecificResource",
"value": "vase",
"source": "https://www.wikidata.org/wiki/Q191851",
"purpose": "tagging"
}
],
"target": {
"source": "https://cdli.mpiwg-berlin.mpg.de/dl/photo/P123456.jpg",
"selector": {
"type": "SvgSelector",
"value": "<svg> ... </svg>"
}
}
}
Support for the Common Objects in Context (COCO) data format is pending.
Both VIA project files and VIA annotation JSON files can be imported.
@id is used containing the full URL
of the annotation.classifying, identifying, describing, and assessing,
corresponding to the W3C purposes of the same name. These fields are expected to be radio buttons
or checkboxes, with URIs to the Art & Architecture Thesaurus (AAT)
vocabulary as the option identifiers. If no term is available, the option identifier should be
a non-URI label.When an update event is accepted, you can click on the link in the column titled "Visual asset" to view the image and its associated annotations.