- Download the
.zipfile from the latest release on GitHub. - In Tropy, navigate to Preferences… > Plugins and click Install Plugin to select the downloaded ZIP file.
Select the items you want to add to your IIIF collection (or none if you want to include all items) and select File > Import > tropiiify. You will be prompted to select a destination folder where the exported files will be saved. The plugin will then create IIIF manifests for each Tropy item, create a collection with all manifests, and tile the images so they can be zoomed in efficiently.
“Standards are like toothbrushes, a good idea but no one wants to use anyone elses” - Anita Golderba
To configure how your IIIF manifests will be created, you will need to define a export template mapping the metadata properties you're using to IIIF properties. This is done by labeling your properties according to the following naming convention:
id: manifest idlabel: manifest labelsummary: manifest summaryrights: manifest rights. As per the IIIF specification "the value must be drawn from the set of Creative Commons license URIs, the RightsStatements.org rights statement URIs, or those added via the extension mechanism".requiredstatement:value: manifest requiredstatement. In the plugin options you can control the label and boilerplate text, so "Musee du Louvre" becomes "Attribution": "Provided by Musee du Louvre" in the manifest.homepage:id: manifest homepage. Thehomepagelabel is set through the plugin options (i.e "Object's homepage").metadata:{label}will send the mapped property value to the manifest metadata section with the provided{label}. For example, labeldcterms:creatorasmetadata:Creatorto add a "Creator" entry in the resulting manifestmetadata. Format the values asLink text [link URL]if you want them to be links (i.eExample [https://example.org]becomes Example)navplace:latitudeandnavplace:longitude: manifest navPlace. These will tipically beexif:gpsLatitudeandexif:gpsLongitudebut hey, we're not judgingnavdate: manifest navDate. The plugin will attempt to parse the value to ISO format, so try to keep the property values neatly formatted.
You can also use the same value in multiple places using the '|' separator. So, if you want dcterms:rightsHolder to be both the value for requiredStatement and a metadata entry, you can label it as requiredstatement:value|metadata:Provider. Or maybe you want dcterms:date to be metadata:Date and also the navDate property? Label it as metadata:Date|navdate.
Don't want to have to deal with this? We also provide a standard template mapping commonly used properties (mostly dcterms and a few exif). You can set up your project from scratch to use these or migrate your data using Tropy's CSV plugin.
To configure the plugin, click its Settings button in Preferences > Plugins:
- Choose a plugin Name that will show up in the File > Import menu (e.g. IIIF Manifest).
- Use the + icon at the far right to create new plugin instances (so you can have multiple configurations in parallel).
- The Item template selector lets you pick a custom export template (see above).