Thursday, January 29, 2009

January 29, 2009

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!

Tuesday, January 20, 2009

January 20, 2009

Through some listservs, I caught wind of a year-old initiative of which I was previously unaware: LiWA (Living Web Archive). In its own words:

"LiWA's aim is to develop new tools and approaches that can deal with these challenges and improve archive fidelity, coherence, and interpretability. The strategy is to frame them so that they are more resistant to future changes, by leveraging universal tools like the browser and by fostering community-based responses to new challenges."

In my words, this initiative seems to be tackling some of the pervasive issues with current web archiving technology, issues like capturing deep and hidden web content, and dealing with what they call "temporal coherence." This last concept, from what I can understand, encompasses the following type of problem: if it takes you 2 days to crawl a large site, and parts of that site change during that time period, have you captured the site faithfully?

Topical areas they're exploring include the aforementioned temporal coherence, as well as archive fidelity, spam cleansing, semantic evolution, the social web, and rich media. There are a number of presentations on the website explaining these concepts, and I'll be digging into them this week.

Wednesday, January 14, 2009

January 14, 2009

The semester begins, and it's time to revisit the goals. Here they are, from the beginning of last semester, and my thoughts on what's happened.

Goals:

  1. What is the current idea of a responsible web archiving strategy, including preservation, metadata, access?
  2. Work to refine scope - how much do we want to keep/is feasible to keep
  3. Identify what has been tried, is being tried
  4. Compare these with UNC's situation (resources/collections)
  5. Review current policy and procedure
A lot of progress has been made, and I feel much more aware of what is achievable during my fellowship.

Goal #1 - I have read up on quite a bit of "practice" but even more projection. Institutions are either treating websites just like other objects they would normally ingest, are keeping their distance from collecting websites, or are outsourcing to the Internet Archive. My main discovery is that UNC seems to be with the pack on most of the issues.
Goals #2 and #3 - How much and how often? These are the big questions for harvesting. For our purposes, I feel that selective and routine but infrequent crawls would work the best. Domain-wide harvests are typically done by national libraries, and this seems beyond our scope for now. We also want to make sure we're dovetailing with other institutions in our area, not duplicating work. It would be my hope that selective, routine harvests would fill in a lot of the public records sought by University Archives, fulfilling the university's legal obligations, and also round out current series in the Southern Historical collection.
Goal #4 - As I mentioned above, UNC appears to be milling in the pack when it comes to pursuing a web archiving plan. In order to move ahead, some simple infrastructure and policy commitments would need to be made.
Goal #5 - I feel that this is where I will be starting this semester. Reading on and developing a solid policy and procedure base for archiving websites is, I feel, the best preparation I can give should the UNC libraries decide to begin regular harvesting. This will also support my work with iRODS this semester, which needs a rule base built from policies.