 All right, so our presenter today is Sarah Romkey. She's a graduate of a dual program, M-A-S and M-L-I-S, from the University of British Columbia in 2008. That's not so long ago, Sarah. She's the Archivematica Program Manager at Artifactual Systems. She's responsible for community management, requirements gathering, testing, and release management for Archivematica. And as you may know, Archivematica is an open source software solution for digital preservation. And as an aside, I've met Sarah in person at UBC, or at least in Vancouver, at Enterprise Trust Meeting. So it's wonderful that she's great to speak with us today. And Archivematica is used by Archivists and digital curators to process digital materials and make standards-compliant packages for presentation. So Sarah will give us an introduction to Archivematica, how it's being used at large and small institutions. I'm eager to hear that myself. And then discuss the importance of open source for digital preservation. So I'm going to turn this right over to Sarah. Thank you very much. And thank you, Pat, for the invitation today. I'm very pleased to be presenting on Archivematica to all of you. So as was mentioned in the introduction, Archivematica is an open source platform for digital preservation. So that's what we'll talk about today and talk about how it's being used and how it's designed and what are some of the principles that we follow when we're designing and releasing Archivematica for use to the public. So Archivematica is developed primarily by Artifactual Systems. And we're a company based here in Vancouver, British Columbia. And we're the lead developers of both Archivematica and another application called Access to Memory or ADM. ADM is used for providing access to and describing archives online using standards-compliant description templates. So Artifactual Systems is really a company that's led by archivists and librarians. It was started by a graduate of the same archival studies program that I came through, which the person who started our company is Peter Van Garderen. He's quite well-known in archives and technology circles. And he started Artifactual as sort of a consulting business but quickly grew in software development where he saw some real gaps in the available tools for describing archives and providing access to them and also for digital preservation. So the rest of our team aside from us archivists here, obviously we have a lot of technologies here. So we have software developers on staff and systems administrators who help us deploy and test and develop Archivematica and ADM. But we're really led by an archivist and by our team of archivists. And we start with archival requirements when we're looking to further develop the software. So some of the salient features of Archivematica, it's important to us to emphasize that it's free and open source digital preservation software. And you can see our software license there. So we make all of our code available to the public. So anybody can take a look at the code and understand if you have the technical ability to look at code and understand how software works. And it's all available to you. There are a number of Archivematica users who are supported by us. One of the ways that we continue to operate as a small company is to provide support and hosting for using Archivematica and ADM. But just as many as not more users who use the software because they've installed it from its source and they're using it without any software licensing or so on. I'm going to talk a little bit later about how open source software is never actually free. It's free in some senses and not free in some others. So we'll talk a bit about that later. Archivematica follows best practices and standards. Particularly it follows the OAIS or Open Archival Information System reference model very closely. And that reference model is the closest thing that we have in the digital preservation world to a real standard for how you should be preserving digital content. At least it's the standard offers which we're all operating at the moment. We can never really say that the software is going to make you compliant with OAIS. Anybody who's familiar with the Open Archival Information System reference model knows that there's a lot of elements to that standard that have to do with human beings and have to do with budgetary matters and policies and practices and you can't really use software to make sure that you're compliant with those things. But we follow the reference model very closely and if you use Archivematica then and you're familiar with that reference model then you'll see familiar terminology throughout. We also use a number of other standards that are considered best practice in the community right now. For example, we use Bagot to package content that's being preserved to the system. We provide a way to enter double and core metadata and we have a very, very robust premise in that implementation. My boss Evelyn, who's the president of our company, she's on the premise editorial committee. So we emphasize our premise implementation pretty heavily and we're pretty confident in the way that it's being used. So we're pretty proud of that. Part of being open source in our definition of open source is that we have no barrier to participating in our user groups or community or our documentation. So you can find all of the documentation for using Archivematica online and as much as possible we try to develop out in the open. So we try to put our requirements documentation online so that you can see what's coming up and after a feature has been released you can sort of look back at the development documentation and understand what was the reasoning behind why we developed it a certain way. And the kind of fundamental goal of using Archivematica is to create consistent, system-independent archival information packages. And that's a term from OAIS. So again, if you're familiar with that reference model and you know what I mean when I say Archival Information Packages or AIPs for short. So the idea is that Archivematica is really like a pipeline that you put your digital content in one end. Archivematica helps you perform all kinds of digital preservation actions and we're gonna talk about those a little bit later. And at the end of the process you've packaged your material together in a way that can be understood by other systems not just Archivematica. So it's really important to us that Archivematica can be used to create these Archival Information Packages that if in the future you decided not to use Archivematica anymore, that should be fine. You shouldn't need to continue to use Archivematica to understand these packages that you've created for long-term preservation because you should never be relying on a single piece of software to understand content that you're trying to preserve for the long term. That would just be creating another layer of complication to digital preservation and it's complicated enough. So hopefully there's some doctor who stands listening to this right now because otherwise the joke may be kind of lost on you but we like to say that Archivematica is big only inside. And, okay, at least one person gets the joke, so thank you. So the reason why we say that is because it's providing more than just a way to package things for storage. If you open up an Archival Information Package that's produced by Archivematica, you'll find metadata about the files that you're preserving. You'll find logs that have to do with the actions that have been taken during the process of digital preservation. And you'll find files in formats that are structured in such a way that help protect against software obsolescence. So one of the fundamental problems, of course, of digital preservation, as we all know, is that as time marches on, the formats become more and more risky to use because the software to support them may go away. So we try to keep up with the community best practices in terms of what formats are best for long-term preservation and will normalize the files that you put into Archivematica to suit long-term preservation. Having said that, all of this is very much up to the individual institutions who choose to use Archivematica. There's a lot of flexibility in the system and I'm going to talk about how you can change those rules and make your own rules and decide for yourself what formats should be used for future preservation or if normalization should even happen. You may want to take a different approach to digital preservation and that's very valid as well. So as I said, Archivematica kind of has this fairly streamlined goal at the end of the day for being a complex system that really is aiming to do this one thing really well and then some other things also well that this is really the core functionality. So what we want to do with the content that you process through Archivematica is you want to create archival information packages or apes. And to do that, a bunch of actions are performed on your content as they make their way through the Archivematica pipeline. So we do things like integrity and virus checks, format identification, which is really important just to understand what should be done with the files to continue preserving them and continue processing them and format identification may sound really simplistic but we use tools in Archivematica that inspect the file using more than just this file extension. For those people who have a long history in computing and for anybody who's worked with files that were created long ago, file extensions are not a reliable way to understand files. Back in the early days of personal computing, they were used all kinds of weird wacky ways to indicate that a file is like a memo or a text file or whatever and it doesn't necessarily have anything to do with the file format. So we use tools that allow you to get more precise information about the format that you're preserving. So is it a JPEG but what version of JPEG is it? For example, we do characterization of the files. So making sure that they fit certain criteria for being that kind of file, metadata extractions, the technical metadata, when was that JPEG created and by what kind of camera and that kind of thing. We've integrated certain forensic activities into Archivematica as well. We're really happy to have implemented a tool from the Bit Curator project, which is a project that we feel is a really important one that really aligns really well with the workflows that Archivematica does and their project really just aligns with the same kinds of philosophical goals that we follow here. So you can use bulk extractor from the Bit Curator project, which is something that helps you find personally identifying information within files. We do format validation and you can also do some basic arrangement and description activities and we've integrated a transcription tool into Archivematica as well. So these are all actions. Some of these are actions that you would absolutely want to take on everything that you put into the system. You know, doing a virus check is a pretty basic activity when you're doing digital preservation. Other things may be optional for you and that's all quite flexible in the system. So if you don't want to do transcription of your files because maybe your files don't have text, maybe there are images that aren't, you know, you can just scan those textual documents. So you can skip the transcription activity. You don't have to do it if it's not relevant to your workflows. When you're working with files within Archivematica, I mentioned earlier that we have the option to normalize into formats that are considered better for preservation. So we try to follow as best we can the current standards for what's considered good preservation practice. But as I mentioned, and I'll talk about this in more detail when we actually take a look at the software tool, you can change all of these rules so that they suit your local purposes. We use the Begit specification to package together the AIP together with the logs and metadata and the metadata is all recorded in a METS XML file that has premise within the METS. So you can, for example, Archivematica will automatically record certain premise activities. So any events that have to do with, you know, your buyer's scan, your normalization and format identification, all those things are recorded automatically without any intervention from you. But you can also manually write rights records using the premise standard as well. So if you want to, you know, have the copyright message in the METS file, you can do that, you know, if you need it there for longevity. And finally, just another important characteristic of Archivematica is that it's storage agnostic. So what we mean by that is if you have it installed locally on a server at your institution, then you can be sending your archival information packages when they're ready for storage. They can go to a local server. They can go to a mounted server. They can go to certain cloud storage integrations that we've done. So we've done integrations with Swift, with DuraCloud, with Archivem. So we try to make it as agnostic as possible. Archivematica is not trying to fulfill your storage goal for you. It tries to handshake with as many different storage systems as possible. And the list is just growing all the time and this is part of the model that we follow. So when we develop Archivematica, we use what's called the Bounty Model of open source development. And so what that means is if, say an institution has a need to integrate with a new storage technology that hasn't existed up until this point, then we can develop that functionality for them. Artifactual systems can. And the next time that we release the Archivematica software, we'll include that new functionality in the general release. So everybody benefits from your institution's sponsorship of a certain feature or goal. Another kind of package that Archivematica can make is it can make what's called again using terminology from the open archival information system. It can make dissemination information packages or DIP. So these are packages that are kind of purpose built for access purposes. So whenever possible, we normalize to access friendly formats. Depending on the kind of content that you're trying to preserve, there may not be an easy to access normalization rule to an access format. So, you know, really specialized file formats that are used in certain sectors like, you know, research data and that kind of thing. Sometimes there isn't really a good format to use for access purposes. So when it's not possible to normalize, we just make a copy of the original and that's part of your dissemination information package. And then as far as providing access to your digital content, what we try to do is we integrate or we call it handshake with a number of different access systems. So one is Adam or access to memory, which again is a piece of software that we develop here at Artifactual. And it's used for online description and access primarily by archival institutions. We also have integrations with Content DM, Archivist Toolkit, Archive Space. And we also have versions of this workflow that work with Island Dora and DSpace. But both of those currently work as a deposit system. So the workflow would normally be that users are depositing material to Island Dora or to DSpace. And then the material then flows through the system and arrives on Archivematica's doorstep to be preserved. But we could develop in the future if it were sponsored by somebody who needed it, the flow of content to go in the other direction where you start with Archivematica and send content to Island Dora or DSpace that would certainly be possible as well. So in our experience, different institutions have different reasons for the access systems that they've chosen. And in some cases they have many access systems. We have done a lot of work over the years with the University of British Columbia Library. They're one of our earliest Archivematica implementers and development sponsors. And out of this list, they currently use three of those systems. So they use Adam for some content. They use Content DM for other content. They use DSpace for some content. So there's a variety of institutional reasons, both practical and historical, why they use so many different access systems for different types of material. And our goal is to make Archivematica sort of the center of all of these in terms of the digital preservation activity. So we don't wanna lock our users down to only using certain workflows for access. You should be able to describe content in whatever system makes the most sense for you. And Archivematica's goal is to handshake with that system so that you have a connection between the material that you're providing access to and the material that you're preserving for the long term. So I wanted to talk a little bit about digital preservation to kind of learn generally and what some of the options are. And this is sort of segueing into my pitch for why a system like Archivematica works for many institutions. So you couldn't rely on functionality within other systems. So if you're using a repository such as something like Fedora or Hydra, there are certain aspects of digital preservation that are covered within those repositories within Island Dora as well. That's another good example of a system that covers some digital preservation functionality. And that may be enough for music pieces within your organization. And what I would advocate for is just taking a close look at what are your digital preservation needs? What are the use cases? And what repository are you using and does it cover what you needed to cover for the long term? There was a period of time and just for some people that still exist, we're using a homegrown system. Was their digital preservation works well? So by homegrown system, I mean some kind of application that you've developed in-house. There was a period of time when things like Archivematica and PreservaFend Rosetta, these systems didn't exist yet. And all kinds of institutions were trying to tackle digital preservation and a lot of them ended up kind of building a homegrown system. So some of the things to consider is that you have to maintain that code. It has no community of users around it. So there's kind of a sustainability of the tool that you have to consider. You and your staff are the only people in the world with digital expertise or with expertise in that particular system. So you need to consider that if you want to continue to use like a homegrown system over the long term. We have some users now who are moving themselves away from using a homegrown system and into using Archivematica because they just feel that it's a more sustainable practice for them over time. And one example of that is the Bentley Historical Library at University of Michigan. They've been doing a major development project with us and have been blogging about the experience. And it's really interesting to read that log and to take a look at where they've come from in terms of what they used to do for digital preservation and what they plan to do once they've implemented Archivematica and a couple of other systems for part of their workflow. Another way to approach digital preservation is just to manage all of these digital preservation actions tool by tool. And that's kind of where Archivematica got its roots, actually. Peter Zangardin, he was looking at the landscape of all of the really excellent open source tools that are available for performing different digital preservation actions. So for example, there's tools that you can use for virus scanning. There's tools that you can use for check summing. There's tools that you can use for format identification. And he was thinking to himself, it just seems impossible that your average everyday archvist is going to be able to learn to use all of these tools. So you need a relatively high level of expertise to take this approach. And it's kind of difficult to maintain. It's also very difficult to record all of your preservation actions in a really consistent manner if you're doing that. So recording all of the output from those tools, you're probably going to be either doing a lot of manual work or writing some scripts to kind of connect all of the tools together. However, that's basically what Archivematica does. There's some scripts within Archivematica that are solely used by Archivematica. They're the only tool that we know of that are using them. We've written them to sort of kind of make the tool one cohesive thing. But it integrates many, many tools that are available in the open source world. And we see this as a major benefit because it brings in all of this sort of current best practice and widely maintained and used tools from across the digital preservation ecosystem. So finally, that brings us to digital preservation systems like Archivematica and they come in both proprietary and open source forms. So examples of proprietary versions are software pieces like Pizzerbica or Rosetta and they have very similar kind of goals to Archivematica in terms of looping together all of these digital preservation actions into one cohesive system that is relatively easy to learn how to use as opposed to using all of these disparate tools from the command line and trying to figure out how to maintain all of the output from them so that you can store it with your digital archives for the long term. So why open source? Why do we choose to take this route for Archivematica? So it's been a part of our model of development ever since we started. Archivematica has always been an open source tool and it always will be. We think it's really important for you to be able to understand your system and see what's happening under the hood. Not every user of Archivematica is going to be going into the source code and poking around and understanding what's going on. But at least if you want to and if you have the ability, you can. And all of the output from Archivematica is shared with you in a relatively easy way throughout the tour and I'm going to show you that a little bit in a demonstration later. It's really important to consider the factor of vendor walk-in. So if you want to take your AIPs, those archival information packages that you've made with Archivematica and store them in a totally different system and open them and understand them in different ways, you are 100% free to do that. There's no requirement to continue using Archivematica going forward. And we think that that's really an important aspect and if you were working with a proprietary vendor around digital preservation, I would personally be asking them a lot of questions about what happens when we choose to stop subscribing to your service because that day will inevitably come. When you want to use a different tool or you have to for some reason. Part of being open to us is also using open standards and open formats for metadata and packaging. So by using things like premise and nets and Dublin Core and the OAAF reference model, we're referring to open best practices that are widely understood throughout the community. You also benefit from this sort of network effect of information sharing and constantly improving tools. So I just mentioned how Archivematica uses all kinds of other open source tools. As those improve, they get folded into Archivematica and you just continue benefiting from this sort of widespread use of the tools and also the ability of the users to maintain a community within themselves and share workflows and share ideas and share bug reports and that kind of thing. And finally, you get to actively participate in the future of the tools that you use. So if you have ideas about Archivematica, you have the ability and we welcome you to submit them to the community. Some users are, you know, their institutions are financially able to sponsor new development. Some institutions aren't able to do that, but you can still participate by testing the software, reporting bugs, giving feedback, sharing ideas on the user form. That's all a way to participate in the open source community in a way that's kind of more difficult to do with proprietary software. However, open source isn't all butterflies and rainbows and I don't want to pretend that it is. So we like to say that open source software is more like a free kitten than it is like free lunch or a free beer. So if I take you out for a beer and I pay for it, then I've given you a free beer and there's really very little commitment on your part. There's little that you have to do. But if I give you a free kitten, you have to take care of it. You need to feed it, you need to give it a good home, you need to scratch behind its ears or something that's going to leave you as you're not going to have the benefit of having a kitten maybe longer. So we're very open and upfront about this. We think it's important that our users understand this, that if you're using open source software, you're going to be paying for it in some manner or other. You're going to be either paying in-house staff for IP support and for installation and troubleshooting or you're going to be paying a vendor like us to provide you with support to help you out when you need it or you may be paying for hosting, which is an option as well. You do need some in-house technical ability or willingness to buy these services. So like I say, it's going to cost you in some manner or other. Really, those benefits I just talked about, you'll find the most beneficial if you take the time to be actively participating in the open source community. That's not to say that you absolutely have to be on our user forum all the time to be using the software. Lots of our users aren't really participating in the user forums or the user community that much and that's perfectly okay. But I do think that you get a certain benefit from it that does take time. So if you don't have the time, you may not be feeling the full benefits of using open source. And finally, institutional buy-in, although this is really improving. So years back, like, I don't know, five, 10 years ago, when archivists were going to their IT departments and saying we want to use this tool, it's open source, you have to deploy it on Ubuntu, which is our preferred flavor of Linux as a server environment for Archivematica. IT departments, you know, sometimes will say, whoa, whoa, whoa, you know, we're not into this open source thing, it's too much work, it's too risky, we don't want to do it. But this is really getting better and we've observed this over the past few years that more and more IT departments are happy to participate in an open source project, particularly if there's a community of support behind it and Archivematica is getting enough uptake now that it doesn't scare quite as many IT people off as maybe it's somebody used to. We have a colleague who doesn't use Archivematica, she uses our other software system, Adam, and she was really worried when she went to her IT department to say, you know, I've evaluated all of these different software tools and the one that I really want to use is Adam and it's open source. She thought for sure she'd be shut down, but her IT department was thrilled. They were like, yeah, this is going to be really fun. We get to look under the hood of this software and we get to really know it and we get to play around and help you make some local customizations and that kind of thing and they were actually excited for the opportunity. So maybe that aspect is getting a little bit better. So I'm going to leave this slide and open up a demonstration that I can show you. It won't be so much of a demonstration as more of a tour through Archivematica to give you a sense of what it looks like. Watching a digital reservation system work is not totally thrilling. It's just kind of watching things happen to a bunch of files in sequence. So instead, we'll do sort of a tour of Archivematica and take a look at where you can find user documentation and so on. So I'm just going to, okay. So hopefully now you can see an Archivematica screen. Pat or one of the other moderators, do you want to just confirm that for me? I can't hear anybody else. I don't know if you're hearing. Yes, I could see that. Talk. Okay, great, perfect. So this is what Archivematica looks like when you log into it. Yeah, so Archivematica is a web-based tool. It looks good. Okay, great, great, perfect. So as I was just saying, Archivematica is a web-based. So you interact with it. Most users interact with it through a web browser. So we use Chrome or Firefox, typically. You can interact with Archivematica through the command line if you prefer to do that. But most of our users now, this is how they use Archivematica. So if you are, again, if you're familiar with the Open Archival Information System reference model, then you'll see familiar terminology here. So transfer, ingest, archival storage, preservation planning, access, and administration. These are all sections of that reference model. So that's not to say that by using each of these tabs in Archivematica in turn, that you are fulfilling all of the requirements of that reference model. But it's just to say that when you're taking actions in this part of Archivematica, this is the area of the reference model that you're working within. So the basic idea is you kind of go left to right. So you grab materials from a mounted system like that server or a cloud storage. And you get it into your Archivematica pipeline and you start in transfer. And in the transfer screen, we can see here this gray box that I'm kind of moving my mouse around right now. This is representing everything that's already happened for a transfer that we moved into the system at some point. So this is a test server that we're using of Archivematica right now. So at your institution, you would have your own installation and you might have multiple installations actually and I'll talk about that in a few minutes. So this passage of materials has gone through the transfer process. And here you can see all of these microservices and a microservice is just sort of a category of jobs that need to be performed for the content. So here for example, I've clicked on the microservice scan for viruses and it shows us the jobs that it has to do in order to be able to scan for viruses. If we want to see the output of the tools, we can click on this little gear and it will open and it will show us all of the output. So if you wanted to go through and really see and make sure that everything past virus scanning, you can do that. You don't really need to do that in terms of virus scanning because if it finds a virus, it just completely boots the process and stops it and gets it out of your system because you really don't want to be transferring in viruses into your digital preservation environment, obviously. But the same goes for any of these microservices. They're all kind of grouped together, all of the jobs that are required to do everything related to the microservice. So here for example, we have identify files on that. I was talking a little bit about that earlier, how that's sort of an important thing to do in the most accurate way possible for digital preservation purposes because it helps define how you're going to manage and preserve those files over time. So here if we want to see the output of the tool, we could open it up and take a look. So I don't know if some of you may be looking at this and thinking, you know, I'm not seeing output that makes a lot of sense to me. I'm not really sure that I would be able to understand what's going on in the system. Not all of our users in not all of our workflows really feel the need to look at this output. But my point in showing it is just to show you that it is possible to see it if you want to. And if you do want to learn more about these tools and looking at the output and starting to parse and ask questions to others who have more knowledge about, you know, what does it mean when it says that the command did this and what does this error mean? We do a lot of troubleshooting to looking at this, the output of these tools. So once all of these kind of initial transfer activities have taken place, the material moves into the ingest tab. And this is where Archive Metacris kind of does all of its work that leads up to packaging for preservation and packaging for access if you choose to do that. So here that same example that we were just looking at is actually sitting at a microservice right now that's requiring a human to take the step of giving Archive Metacris an instruction on what it should do. So if you wanted to, you could automate all of the services all the way through and you can do that in this administration tab. So all of these little check boxes here in this list, these all represent a decision point in the Archive Metacris system either in transfer or in ingest. And if you want the same actions to be taken every single time, you can just click and choose what the action should be. If you don't want it to happen automatically, you want a human to actually click and make the decision on a case-by-case basis, you leave it unchecked. So we have certain institutions who are running Archive Metacris at such a scale that they have multiple Archive Metacris installations which we call each one a pipeline. So multiple Archive Metacris pipelines running for different purposes. And part of the benefit of running more than one pipeline is that you can preconfigure for certain kinds of material. So for example, we have some institutions who have born digital material as well as digitized material. And they run very different processes based on what kind of material they're processing. So for born digital material, you're going to be concerned with things like finding, personally identifying information, for example. You may be only wanting to normalize for preservation and not for access because maybe it's your, you don't currently have a policy for providing access to born digital material. You may just have different processes depending on your local needs and your policies. So in that case, it'd be advantageous to you to have one Archive Metacris installation that's running for born digital and another that's running for digitized that doesn't have the same needs. If you digitize the material, it's unlikely to have personally identifying information that may not be of concern to you. So you can preconfigure the pipeline so that it skips that step and you don't have to run the process. Once material has been packaged for preservation, you'll find it in the Archival Storage tab and it's listed here for easy access but it's really just pointing to its ultimate storage location. So in this case, because this is a test server, it's just the storage location is just on the same server that Archive Metacris is installed on but if you use a service like DuraCloud, for example, you can store your archival packages in DuraCloud and retrieve them from here just for easy access. So you can do searches for material if you want to find certain things. You can do a file search so that you can find individual files just in the packages that you've stored. The Preservation Planning tab is a really interesting area of Archive Metacris and I wanted to talk about it a little bit. So we've made the Preservation Planning tab so that it lists all of the rules and commands for the different preservation actions that you take in Archive Metacris. So alongside here, we have things like identification, characterization, extraction, so that's like extracting packages like zip packages and things like that, normalization, transcription and so on. So if you wanted to take a look at some of the rules that Archive Metacris is going to follow to do certain actions, you can do that through this screen and the rules that Archive Metacris comes with when you install it, it comes from something that we're calling the Format Policy Registry. So we maintain this database of formats that all Archive Metacris installations can get access to. But if you wanted to, you could make local changes. So here, for example, under normalization, I'm going to go to rules and I could search for a certain format. So for example, if I wanted to search for VNG or digital negatives files, then I can see that for different versions of a DNG, it has rules for access and it also has rules for preservation. So for access, we can see here that if you tell Archive Metacris to normalize for access by default, it'll take these various versions of digital negatives and it will make a copy of them to JPEG using a script that we're calling Converge and it's using image magic as the backend tool for that. So if you wanted to replace that, say, you have an access system that needs tips, not JPEGs. So you could replace the rule. I'll just load in a second here. You could replace the rule so that it uses a different format. So if you wanted to, say, change it to tip instead of JPEG, you could do that. If you want to change the command, you can do that as well. So again, under normalization, I'll go to commands and you can see the different commands that are listed here. So if you want your tip files created in a certain way, you can open up this command and you can replace it. And if you have some knowledge of the tool that it's using and how it works and how you write commands for it, you can make changes here. So for example, you might want to write a command that makes a tip of a certain size because that's what you need for your access system or something like that. So there's a little bit of programmer knowledge that would be helpful to have here, but it's the kind of knowledge that I think a lot of archivists and librarians and curators would certainly be able to learn and obtain if they don't have it already. And if not, then somebody in your IT staff would probably be the people to help you with this. And you can always ask for help on a major forum as well, of course. So I just wanted to show you that this system of rules and commands is meant to be quite flexible so that if you have local needs, you can address them. We have sort of a future goal for this format policy registry to take it and make it so that you can share your rules with others. So for example, one of the sort of powered users, I guess you could say on Archivatica is MoMA. The Museum of Modern Art in New York, they're using Archivatica to preserve time-based artwork. So things that are like, you know, video recordings and things like that. So a smaller museum may not feel like they have the same level of expertise as a place like MoMA. So they may want to look to MoMA's rules and say, whatever you're doing for preservation planning, we wanna do similar things here. And they'd be able to share rules back and forth if you choose to do so. So that's just kind of an idea, vision for the format policy registry that we have. Hopefully someday we'll be able to achieve that. Certainly, if it was of interest to an institution to sponsor it, it would be really interesting talking to them about it. But we've set it up in such a way that that kind of abstraction from the system is possible. So that you don't have to use the kind of out of the box rules that Archivatica has. So I'm gonna take just a few minutes to talk about a few of the documentation sources for using Archivatica. And then we'll leave the rest of the time for questions. So this is the Archivatica website. You can find it at archivatica.org. And under documentation, you can find documentation for all of the recent versions that have been released. So if you are using version 1.4, you'd go to that documentation. And the documentation, similar to the software itself, also refers to the open archival information system reference model. So here under transfer, you'll find instructions for all of the relevant activities that you do in the transfer tab, saving an ingest, and so on. So all of our documentation is completely open. Anybody can access it. You don't need like a login or anything. It's not kind of paywall. So feel free to take a close look at that if you're interested. We also maintain a wiki. And the purpose behind the wiki is, well it used to be our only source of documentation actually, but now what we use it for is primarily for development purposes. So if we go to the development documentation section of the wiki, we can go to say, for example, requirements and look at a feature and find out more about how it was developed and why. So one of the big things we've been working on right now is this new tab that we've been developing with the Betsy library that we're calling the appraisal and arrangement tab. So if you wanted to read up on some history and kind of figure out like why we did this development and how, see some early iterations of what it was going to look like and then see how that changed over time, then we try to make as much of this kind of documentation as open as possible so that we just think it makes the software more usable by more people if you can understand how it was developed. And then finally, if you really wanna get into the nuts and bolts, you can look at our code. So we use GitHub to manage our code. You'll find us at github.com slash artifactual and you'll see all of our projects there, including Archismatica. So if you really wanted to get into the code and see how Archismatica is developed and you have the technical knowledge to do that, then you're welcome to do so. So I'm gonna stop sharing my screen so that I can go back to the blackboard. And I'm ready to take questions from any of you. So please go ahead and shoot. I think you could either type questions into chat or use your microphone if you have it connected to the desk. I see Laurie is typing something. Did you wanna take the mic, Laurie? No, no questions for me. I have my own Archismatica sandbox, as you know. Well, I'm a pro Archismatica person and I love the work they've done. And I think it's been a very useful thing for our community. Excellent, thank you so much, Laurie. Anyone else have any comments or questions? I have a question. Okay, go ahead, Sandy. What was the name of that museum in New York? I didn't hear that, it was MoMA? Yes, it was MoMA. Okay, thank you. So MoMA, they use Archismatica and they also helped us develop a new system that we're calling Binder. They're currently the only user that we're hoping to change that really soon. There's some, they had digital preservation management needs that Archismatica wasn't really meeting on its own. So things like reporting and statistics and connecting, kind of connecting the dots of things. So if you're preserving an artwork that requires a certain piece of hardware to run it, how do you manage that information? So we built this new application for them and it's called Binder and we've open sourced Binder. We've put the code up online, but there's some challenges relating to making it work like outside of the MoMA context, so we're currently pursuing opportunities to make it more generally usable, but if you look on YouTube, if you search for MoMA Binder, you'll find some presentations and screen tasks about Binder and why it's important and how they're using it, and it's a pretty interesting tool. So I'd recommend taking a look at that, if that interests you. Particularly if artwork preservation is of interest to you, it's a really interesting tool to look at. I guess I need digital artwork really. It has nothing to do with managing, you know, like physical conservation of art. I'm going to thank you for presenting to us today and turn off the recording, and if anyone has a last minute question, I'm sure you'll be able to get it in. So thank you, Sarah. Thank you.