 Good afternoon, as you can see my title for my presentation is slightly different from that dry, terribly unappealing thing that it used to be. Yes, so I will say that the presentation is slightly probably a little different to what's advertised and as I go through the presentation you'll understand why. So I hope you get something good out of this. Anyway, so at the beginning of the year, Victoria University of Wellington Library embarked on what we thought we decided Delta is an ambitious plan to implement a new digital asset management system. The cornerstones of the new system would be two existing collections, our institutional repositories and the New Zealand electronic text collection. Driving the need for the new system was outdated infrastructure and a need to implement digital preservation for access as one of the requirements of what we were attempting to do. I had hoped at this point to be at the stage where I could share with you more of the progress on what we had developed, including screenshots and potentially even a live demo sort of thing of where we had got to. But sadly, as is sometimes the way with projects, we're not quite there yet, which does mean this presentation isn't going to be quite what I originally intended. I will say that one of the main reasons is we did a nice lot of requirements and we had an idea of what we would want to do and then we got the responses and chose one that didn't fit in with quite what we planned. So we had planned to go to a cloud-based service and in the end the service we chose was internally hosted. So we had to go through the whole process of setting up servers and going through that, which has extended the timeframe for the project. So it's not quite going to be what it is. There will, however, be kittens and maybe water. I was told, I was just suggested that maybe I should go since I wasn't going to be completely going with screenshots of everything, that I should go completely esoteric and have completely random slides so that we didn't get PowerPoint death of brains in the audience. I have gone a little bit like that, so there won't be too many informational PowerPoint things, but there might be things like kittens. So basically in the last few weeks I've had to sit down and ask myself what can I share with you guys and more importantly what would I, if I was you, would like to hear. I had developed a sort of presentation around that, but it got changed at the beginning of last week when we had that little earthquake. It sort of actually impacted a little bit quite heavily on what I want to talk about, so there is going to be a little segue into recent events as we go through. So basically the progress, so basically in this presentation I'll cover the progress we have made a little bit so far. Also some of the learnings the project team has come to and then maybe a few other things. So basically where have we got to? After an intense time where we set requirements for projects, we put out a call for response to a request for tender and evaluated a number of responses to that request for tender call. The library selected Rosetta from Ex Libris as the application at the centre of our digital assets management system. As you can see Ex Libris, they like to brand everything. It does mean that Victoria University is now the first tertiary library in Australasia that is going with one vendor to do their digital asset management system, and their library management system and the discovery. So we're on the Rosetta Alma Primo integration sort of loop, which is interesting. We did select at the start of it a name for it, which I'm going to share with you, which is Wairito, which means deep water. And it's quite been apt as often we've felt we've been treading in deep water as we develop the new dams. We're currently working quite intensely on the workflows that will allow us to put things into the new system once it's going. And this is where we sort of segue a little bit into the last week and the earthquake and the effects on having a major thing happen to your work team at a very integral part of the time of the project. So at the moment we're really, really heavily involved and if you don't know that we're outside, we've been locked out of our library and our work spaces since the earthquake and we won't be back in probably until the week after next. So it's interesting. Fundamental core of the project is digital preservation for access and with restricted access to the physical resources, the importance of digital in its longevity has been reinforced within our community. In the last week indeed a number of academics have already commented on the ability to access digital collections. This is sort of highlighted to me especially the importance of a rigorous digital preservation strategy which we are trying to achieve in the dams. The team within the library has done an amazing job in maintaining momentum on the project at a crucial point in it while working from a range of remote work spaces. The team for the project is mainly based in Rankin Brown, which I've said, which is closed and will be open 5th of December as the latest. That means the team has been juggling project work along with core business and doing so from off-site. I just want to sort of delve a little bit into how this works with telecommuting and that off-site work for something like this. We had thought we'd set up for off-site work, everybody, and we had gone through some plans about, you know, as you do after Christchurch and everything previously, what would happen and you make plans. And we'd set ourselves up so we thought we were in the right spot. But what we found out very quickly is we hadn't quite got there. So we initially had to work on ensuring that people could actually do the jobs they were doing. This meant a lot of working on VPNs and remote accessing and trying to actually get in because the project where it's at at the moment is a lot of... It's all behind firewalls within the internal structure and it's all linked to where we sit within our building. And as we aren't in there, getting people into that was the problem. And we've worked through it and our team has been quite good and has done a lot of work amazingly well from their home lounges. And I just thought there was something that's impacted on me so I thought I'd just sort of bring that up here. So we'll get back to the project, hence the kittens. As always with implementing a new system there are numerous challenges to come to grips with. Intellectually we've had to come to terms with the new system, how it deals with assets and the digital preservation concepts that underpin it. Also there's new scheme, new metadata schemas to learn and new ways to look at workflows. We had to look at our current collections and see how they are configured, what's the underlying architecture and what it can do to fit within the new system. There's been a lot of looking at revisiting some of the old choices with things like our legacy heritage collections in the New Zealand electronics text collection and seeing what's applicable and how we can bring that over. One of the more complex elements that we are accounting is in configuring the NZETC to ingest is the varied ways that we put things out there to people. So no single item within the NZETC has a singular makeup. We can't say that all items will have X, Y and Z because they might have X, Y, Z and then A, B, C and D. Many of that is linked to the fact that at the moment it's very heavily focused on one core element which is the TEI, which is Text Encoding Initiative, which allows for deep research within to a text. But then from that we've got a varied other things. So one text might have pages for every page, other ones might just have images that have been cropped out and no page images at all for things. And some of them have, like in recent years, we've been concentrating on capturing all our images into form. But previously we only have maybe JPEGs or GIF images for bits. So there's a complex process of merging in what we've got and then massaging it into a shape that we can then ingest into the new system. There's also the complex link data authority system that highlights people places within the NZETC works that we've got to work around. With the way that the new system works, how do we ingest that into that and how do we maintain it? What do we do for the workflows for that? That's one of the things that we're trying to work through at the moment as it's fundamentally different. Also, yeah, so one of the complexities that we have been most keen to address is the links into the NZETC. We're aware that there are thousands of links from numerous sources into the NZETC and we're trying to be conscientious library land citizens so we don't want to break them as much as possible. But the new system doesn't really lend itself to reusing the old URLs so we can't do one-to-one matching. So we're going to be having to find out what we can do to bring those over. So we've been taking a sort of a green fields. One of the things we've been doing has been to first of all put everything into the internet archive so we're working with taking up a subscription to archive it to ingest all of the NZETC and all those sites into it. And then as we work through, we will be going through and working on mapping links and redirects to say when people come from this link, where do they go? So that's another aspect of what we're working on. So we will be actually ending up having a sort of a green fields effect with new URLs for everything but we are working on trying to make sure that we preserve the links in and we match them across, match them to and through. This does mean that we have a lot of work of looking at and as we're doing this we're looking to see what will come forward in the future so it's a lot of not just planning about taking old things in. When we make this decision now, how is it going to impact in the future? Because I think from what we've discovered and looking at this and something that I'm very aware of is that we tend to do some of these projects and we plan for the now and the short term and there may be a little bit of medium term of how long we're going to maintain it but we don't tend to think often about an exit strategy for when the technology gets overcome, the platform becomes not fit for purpose and whether the choices we make when we're setting it up are going to make it easier or harder for us to then take those things from an existing place and put them into a new one and at the moment we're in a complex position where we're trying to take some old decisions and they're complex and fit them into a new one so as we're doing that we're looking to see how the decisions we make now mean when in 10, 15, 20 years when Ex Libris is no longer functioning or some newer digital preservation system comes along that's going to do everything we want and is much better in this open source or something like that. How easily is it going to be for us to take the decisions we make now, take them out and then put them into the new thing. So yeah, I'm not sure why I've got digital planning and digital preservation there. It's probably because I was a pointer for the fact that a digital preservation is important for everything. So anyway, in conclusion, I know it's a little bit short and that's mainly because we don't have quite as much as I had hoped and I do apologise that to share. We are on track to deliver our new dams next year and probably hopefully next year at this time we won't be treating so much water but we'll have dived fully into our wider ecosystem and we will be exposing new collections in new ways and you'll have seen what we have done and hopefully we'll find it good. So yeah, thank you very much. Questions? Time for questions. Hey Michael, I just thought it was really cool to using Internet Archive the way you are and I just wondered if you would expand on it maybe for the audience a bit more because I think it's a use that more people could make use of it and I'd like to hear yours a bit more. Yep, so one of the things we're all about digital preservation. It's an interesting aspect of it as we're introducing the dams to do to make sure that we've got digital preservation right for us at the beginning and one of the processes we're using is a free third party resource to digitally preserve our old things because they're more set up to do that. This is the progress we've made so far in ingesting. So the Internet Archive does its big crawls and it comes along and just randomly grabs things but if you've got a big and deep complex site they just sort of skim it and your stuff won't be in it as much. So they've got another service where you can archive specific collections and do specific things with it to put things in. So we chose to do that and we took a subscription and at the moment we're running a crawl across the NZETC to ingest it which is going to end up at about 1,600,000 documents which is basically webpages and images and JPEGs and all those sort of things and it's been going for three months and it's probably going to take another two months to finish so that's the way they set it up. But one of the things that's really useful actually getting into that is that it crawls not only your site but links into and out and looks to find ones that you should put in there and other ones so there's got a list of exclusions and inclusions from a different websites. So one of the things we've identified from that is we'll be able to take the reports that will generate from that link to and from and use that to double check what we think are linking to and from to do that marry up. But yeah, it's been quite easy to do too and it's really useful. Paul, where's my kittens? I'm not asking this on behalf of my neighbour. Michael, I just wondered is the NZETC not already archived in the NDHA? I don't know, Ross might be able to answer that question. Not in a very public way that we can get access to. So with one of the benefits for doing what we're doing is they will then package up our end result into an archive into an archival standard for digitally preserving your website and then we can pull that out. So in the long term, our plan is to let them archive it in there, they can transform it and then we will download it and re-ingest it back into the Wairitu and probably use the open source way back machine to be able to show it again through our own internal systems. But for the NDHA, we did have worked a little bit with the National Library to try and do digital preservation and preserve whole sites in that complex manner in there. But like the Internet Archive, I believe that the level of skimming that they did for capturing things like the NZETC didn't capture everything, it was a very high level. Yeah, not trying to, yeah. Obviously they need to mic up the entire auditorium. We should pass that on to Papa, put mics down. Thank you very much. Michael, I was just thinking about your solution and the fact that Rosetta is good at preservation processes and reasonable at digital asset management system but is not a front-end and that part of your difficulty is going to be for your end users actually having experience where they can still interact with the NZ art tech centre collections. So I'm just wondering, and I think we've talked about a little bit as now the time where we should be thinking nationally about those techs collections and thinking about a building user experience right across all of New Zealand's techs collections and then your requirements that are just for NZETC would be so much more secondary and would take some weight off yourself of having to deliver a front-end if we combined them all and built that. We've talked about for a while that corpus of techs that we could use nationally for techs mining and so on. Yes, sounds good. I think, yeah, one of the things I probably should mention, the Rosetta system is primarily being used as a deep archive for digital preservation and is not so robust on the front-end so we'll look to expose things through the Primo Discovery layer. So one of the things we are aware of is that we're going to have to do a lot more development on that user experience in the end. Because we're doing the Greenfields approach we will have for a time dual systems so we're not going to take down the NZETC or our IRs until we are confident and comfortable that how we are then exposing it through the new system is the right way and as everyone, the user is getting the right experience. Integral to that is they tell us that it's the APIs so we haven't, it's one of the next stages of the project is exploring what the APIs actually do so we can look at those front-end customisations and I imagine that using this there will be a little bit of work that in there that will end up being able to share it across so that if other places look at APIs and take out that what you're talking about is going to have to, the same work, we're going to have to do the same work anyway if you get my meaning because we're going to have to do the APIs, if we do the APIs to feed out to a national one we're still doing the APIs to feed out to what we need to do. So it could be, but it won't be, so there will be, does that make sense? I think. Yeah, although one option could just be to give your archive a dump to Digital New Zealand and say, here could you make us a front-end? We could, I guess. I'm not sure how much they would like us doing it. It was kind of a bit funny, but serious too. Yeah. So we're a public library who has added catalogue records for all the components, the contents, the electronic tax collection. Yep. So if we're now able to start telling people they can get these obscure bits of New Zealand published material directly and they can find it in our catalogue and go and read it straight away. Well, those links be broken at some stage and we'll have to be remade. So we're hoping with our redirects that they won't, the way we want to do the redirects is they won't directly be broken. You'll be fed off into either the closest new thing or off to the Internet Archive. Internet Archive. But one of the things we do have on our plans is, before we get to that, is we will be looking to have a bulk pace where you can download the catalogue records for them and replace them. So we're looking to make sure that we do have, you know, that where you've got the records already, we will be minting new records and they'll be easily downloadable. We did this through Qatui, so we didn't actually have to do a great deal. So Qatui wouldn't have to do a great deal either. Hopefully not. If we get it right, we're trying to get it right. We're still working on it. But we are really well aware of the amount of records that are in different library systems that link into it, as well as the ones that are from in, like Tiara and the ones that are in Wikipedia and the links all over the places that come in. So we are very aware of that and we really don't want to break them badly. But you've seen that this is likely to happen again in 10 or 15 years? I would imagine the way that I see it, so I'll probably get in trouble for saying that, but the nature of digital projects like these collections and things is there's always a flux of change and there's always new things that come along. And I'm not sure that it would be the best will in the world that you can create a system now and mint handle.net or persistent URLs that will always go to that, that you can't say that in 10 to 15 years those won't be broken with people going along and saying, well, the system that we've got doesn't fit anymore. We need a new system and we can't transfer those over, so we have to do new URLs. We'll just have to build that into our workflows that we're always going to have to be being aware that things that are in our catalogue are pointing at objects that may not be where they were originally. We'll always have to have catalogues. Yes, we'll always have to have catalogues in indexes. Thank you. Wrap it up. Thank you very much.