Mia Ridge  0:00  
Hi, thank you for having me and thank you for all the comments today. So I'm Mia Ridge I'm digital curator for Western Heritage collections at the British Library. When I joined the library in 2015, I became the product owner of the Universal Viewer at the British Library. So some work had already gone on with the viewer. But they were in the middle of development, developing new features. And also I was involved in the process of negotiating the metadata that went into our IIIF manifests, so looking for commonalities across very varied collections, which was a quite complex task. And I think my comments will build on many that have gone before. But my one piece of advice would be doing user research and usability testing to help prioritise and clarify your requirements. When I began, I inherited a really long list of requirements, some of which of course contradicted each other. We didn't have the resources to implement them all. And I didn't have the related commissioned usability work, which was really useful in terms of thinking about how we might better group items and functions on the viewer itself. I didn't have that at the start. So, and user research is usually a nice way of cutting through contradictory requirements within a project because if it's user focused, that can take away the heat from some of the other discussions, particularly in a library that has really quite varied collections. I think, two other things that I think are important, would be having a workflow that allows frequent updates to code and allows you to iterate on your manifest design so that you can work with a small sample of representative items and iterate and test and actually show people what you're working on. Before you go back and create manifests at scale. One of the issues the library faces is just the sheer number of items. I think it's 800,000 manuscripts in 14 million books and 4 million maps and whatever. So, once you've created a manifest that's kicking off quite a large process. So, as Andrew's comments bear out there some expectation management about how long that takes, and also outside of the project itself, understanding the complexity of systems in which content has been held for many decades in cases and how complex the process of migrating that into systems that were IIIF capable was going to be. The project that I worked on ended in late 2016, and we're really only just picking it up again now, and that's a resourcing issue. We would have hoped to have kept working on it in the meantime that I think where you can work iteratively, and now we're in a much better place in terms of working with the community and working with updates, they're producing and not allowing having systems that allow us to develop something that's specific to the BL's needs but also stays in sync with what's happening in the wider UV community, and probably one final piece of advice is just that it's the IIIF community and the Universal Viewer communities generally full of lovely people who are quite happy to share what they know. So actually it's been quite enjoyable being part of that community.