Tom Crane

Code that would need changing: https://github.com/wellcomecollection/iiif-builder/blob/30afa831afedf79182880563b20912eb2b038dc4/src/Wellcome.Dds/Wellcome.Dds.AssetDomainRepositories/Mets/Model/ModsData.cs#L74

Needs to wait until there are some examples of this in the Catalogue API.

After starting work on this I'm inclined to leave this issue alone. The data is more useful than I thought, and: There's a problem with the second para above; if...

atm in DLCS / Orchestrator the `/auth/` path is reserved and is DLCS's impl of Auth v1. We rewrite for Wellcome to remove the customer `2` but the raw URL...

For now I've added some info as _Presentation_ metadata - for display to users, rather than machines - we can come back to a little model later. I've put these...

Incidentally, matches this: https://leedsunilibrary.wordpress.com/2021/01/06/a-year-and-three-months-as-a-bridging-the-digital-gap-trainee-in-leeds/ > As a result, users will be able to explore this collection and discover several features for each digital file – such as file format, size...

Just occurred to me that Manifest-level metadata could provide info like _total size of this item on disk_ by summing the file sizes; a little report as a summary field:...

Result of discussion - agreed that we should do this, @jtweed where? Is this RFC-size? Seems a bit too small for that. I can write it up, wherever it needs...

https://github.com/wellcomecollection/docs/pull/30

The above RFC is still a Draft PR. Thinking about timing of this, and the dual-running suggestion of #4683, we shouldn't have the new DDS using one set of rules...