Here's an update on what I've been working with in the last few weeks. It's been difficult trying to figure out where to go this semester, especially while I'm waiting for some technology-related projects to move forward.
1. iRODS: I've been thrown head first into iRODS in an incredibly short but very interesting class. I've gotten the client installed and my group is now working on identifying policies we can use to create rules.
2. Web Archiving Policies: In continuation from last semester, I'm trying to draft some web archiving policies using the Collection Plan Template from the Web-at-Risk project as a guide. This has proven to be more difficult and more simple than I expected. Here's what I mean. Because the UARMS impetus for collecting websites is partially grounded in North Carolina Public Records Law, much of this information can be taken directly from the department's current scope used for paper records, and can be based on the department's established mission. On the other hand, areas dealing with digital object preservation, migration and workflow are more difficult to determine without any overarching digital object policies to which I can refer.
I know from past work experience how people abhor the word "policy." But I'm coming to see that policies can end up serving a unifying purpose and also save work for those down the road. The difficulty, I guess, is in having all interested parties agree on one policy. It's a lot of effort up front and probably seems to delay "real" work. Peddling around on your own can end up giving others something to work with, and I hope that will be the case here.
3. A Little Experiment: I've decided to try an experiment in order to determine exactly how many scheduled records would be pulled in from websites. Using a random sequence generator, I've selected 20% of the UNC departments with completed records schedules. I'm going through and listing the series that would normally be transferred to UARMS at some point in time. Then, as best I can, I'm assessing the departments' websites for those series. Although collecting records would not be the only reason we would harvest the sites, I'm interested in seeing exactly how often scheduled records are put online. Are departments really posting documents UARMS would normally collect in print?
I recognize that this is limited in certain ways. For instance, those who have completed individual records schedules may be more likely to publish their important documents online in the first place. Second, those who do not have completed records schedules are probably departments we would or should be more aggressive in harvesting. I may also fail to locate the records during my survey of the website. Still, I want to make sure I have a closer idea to exactly what a web harvest would accomplish from a public records compliance angle, and I think this little experiment will help.
4. Ongoing Efforts: I'm reading any new publications I come across on web archiving. I'm alsoruminating on my poster presentation coming up in April at DigCCurr 2009. With the delays I've had in getting some web archiving tools set up, I may need to take that poster in a different direction. There's still a bit of time, there. Whatever it ends up being, I hope someone will find it useful!