Known formatting list only, can be expanded as required.
{assetPath} is a PathTemplate value that can be replaced, this PR adds functionality to handle a format (e.g. {assetPath:3US}). 3US is the only currently supported format, this will replace 3 underscores ___ with a slash /.
This will allow identifiers that contain invalid characters to be reflected back in "id" properties.
Formatting is only supported for assetPath - {customer}, {space} etc left as-is.
assetPath is more than just the "asset" part of the Id, it's the "asset" part and also any asset-delivery parameters. E.g. for /iiif-img/2/1/foo/full/!1024,1024/0/default.jpg it will be foo/full/!1024,1024/0/default.jpg so any path rewrite formatters would need to be aware of this to not collide with IIIF parameters.
A concrete examples is, for an image with Id 2/1/foo___bar-baz being replaced on info.json:
Known formatting list only, can be expanded as required.
{assetPath}is a PathTemplate value that can be replaced, this PR adds functionality to handle a format (e.g.{assetPath:3US}).3USis the only currently supported format, this will replace 3 underscores___with a slash/.This will allow identifiers that contain invalid characters to be reflected back in
"id"properties.Formatting is only supported for
assetPath-{customer},{space}etc left as-is.assetPathis more than just the "asset" part of the Id, it's the "asset" part and also any asset-delivery parameters. E.g. for/iiif-img/2/1/foo/full/!1024,1024/0/default.jpgit will befoo/full/!1024,1024/0/default.jpgso any path rewrite formatters would need to be aware of this to not collide with IIIF parameters.A concrete examples is, for an image with Id
2/1/foo___bar-bazbeing replaced on info.json:/{prefix}/{customer}/{space}/{assetPath}=>/iiif-img/2/1/foo___bar-baz/info.json/{prefix}/ark:{assetPath:3US}=>/iiif-img/ark:foo/bar-baz/info.json