While we're waiting for the test server to be set up, I've decided to start investigating policies, guidelines and workflows.
I've started two new wiki pages. The first is a place to aggregate mission statements, informing policies, and example web archiving policies. I've begun by collecting information from the University Library, University Archives and Records Management Service, the North Carolina Collection, North Carolina General Statutes (Public Records Law), and information from the UNC IT department on website policy. I've only found one bona fide web archiving collection policy thus far (thanks to the British Library), but I think more are out there. It's unfortunate that more libraries and archives don't put their collection policies online. I'm having to cobble together ideas based on articles I've read.
The other new page is a place to start formulating a workflow for web archiving. To help me make sure I'm accounting for all parts of the process, the workflow will be informed by the infamous OAIS reference model. Right now, what I've written is at a very high level, and I'll slowly add in more detail, especially once I can do some test harvests.
Friday, October 24, 2008
Monday, October 20, 2008
October 20, 2008
We're currently in a holding pattern here, waiting for access to a test server hosted by ibiblio. It looks like this server has sufficient functionality to begin testing at least one, if not more of the web archiving tools I'm interested in. This will be a great opportunity to see what these tools can do, and to determine which ones seem best for our situation.
In the meantime, I've been doing some more reading and adding to the wiki. I've also been performing a basic site analysis of several high-profile and highly desirable UNC websites. This analysis includes trying to get a sense of how deep and broad the sites are, what sort of file formats are included on the site, how much they link out, if their pages include dynamic content, and who might be interested in the site's information. I've gotten a number of sites that I think would be viable for test harvest.
I'm now looking at a list of North Carolina sites not affiliated with UNC that have been identified as high priority for harvesting. This presents more of a challenge for a number of reasons. First, many of these sites have more dynamic content, like calendars and blogs, and a greater number of links out to related resources. Another additional step that with these sites involves clearing copyright and/or obtaining permission to archive. Many web archives operate with a blanket "take down" policy (Internet Archive and MINERVA, among them), meaning they harvest first and then post a general statement notifying those who object to their harvest that they will remove the materials in question. But these policies are generally used when the harvesting is done on an unselective basis, because of the infeasibility of trying to identify and contact all of the copyright holders. Best practice for selectively harvesting sites really dictates contacting the different agencies and at least attempting a good faith effort at requesting permission to take their materials as well as to provide access to them. Some even suggest that it might heighten your archive's profile and increase its scope (Žabička, 2006, p. 3). Archives like PANDORA and WebArchiv both follow this protocol. Negotiating for harvest not only serves to avoid contentious encounters with webmasters or agency representatives, but also shows that you are attempting to be a responsible steward with your materials.
Žabička, P. (2006). Digital cultural heritage and cooperation of memory institutions. Paper presented at the 1st Colloquium of Library Information Employees of the V4+ Countries, Banska Bystrica, Slovakia.
In the meantime, I've been doing some more reading and adding to the wiki. I've also been performing a basic site analysis of several high-profile and highly desirable UNC websites. This analysis includes trying to get a sense of how deep and broad the sites are, what sort of file formats are included on the site, how much they link out, if their pages include dynamic content, and who might be interested in the site's information. I've gotten a number of sites that I think would be viable for test harvest.
I'm now looking at a list of North Carolina sites not affiliated with UNC that have been identified as high priority for harvesting. This presents more of a challenge for a number of reasons. First, many of these sites have more dynamic content, like calendars and blogs, and a greater number of links out to related resources. Another additional step that with these sites involves clearing copyright and/or obtaining permission to archive. Many web archives operate with a blanket "take down" policy (Internet Archive and MINERVA, among them), meaning they harvest first and then post a general statement notifying those who object to their harvest that they will remove the materials in question. But these policies are generally used when the harvesting is done on an unselective basis, because of the infeasibility of trying to identify and contact all of the copyright holders. Best practice for selectively harvesting sites really dictates contacting the different agencies and at least attempting a good faith effort at requesting permission to take their materials as well as to provide access to them. Some even suggest that it might heighten your archive's profile and increase its scope (Žabička, 2006, p. 3). Archives like PANDORA and WebArchiv both follow this protocol. Negotiating for harvest not only serves to avoid contentious encounters with webmasters or agency representatives, but also shows that you are attempting to be a responsible steward with your materials.
Žabička, P. (2006). Digital cultural heritage and cooperation of memory institutions. Paper presented at the 1st Colloquium of Library Information Employees of the V4+ Countries, Banska Bystrica, Slovakia.
Thursday, October 2, 2008
October 2, 2008
While reviewing the proceedings from the recent iPRES conference, I stumbled across a very interesting JISC-sponsored project: PoWR. First, the acronyms: JISC stands for the Joint Information Systems Committee, whos mission "is to provide world-class leadership in the innovative use of I[nformation and] C[ommunications] T[echnology] to support education and research" (JISC website). PoWR stands for Preservation of Web Resources. It is a short-term project funded to "organise workshops and produce a handbook that specifically addresses digital preservation issues that are relevant to the UK H[igher] Education] /F[urther] E[ducation] web management community" (from the PoWR website). The main method of communication for the PoWR project is through the blog linked above. Many of the posts are directly relevant to the challenges of archiving websites at an institution of higher education, including sections on records management, case studies, and web 2.0. I also listened to Brian Kelly's presentation, which gives a great overview of the project in 13 minutes. Check out the case study at the University of Bath when they used an innovative approach to try to "motivate the techies" by drawing parallels between their print prospectus (or catalog, for us Yanks) and the website.
Even better, PoWR has released a draft of their handbook, which they will be finalizing after they receive feedback. I haven't read through the entire thing yet, but I've already gotten to the section on making a case for web archiving at your institution. In scanning the handbook's contents, it looks like a list of the same issues I've been considering during the past weeks. It's quite exciting and I recommend a peek.
Even better, PoWR has released a draft of their handbook, which they will be finalizing after they receive feedback. I haven't read through the entire thing yet, but I've already gotten to the section on making a case for web archiving at your institution. In scanning the handbook's contents, it looks like a list of the same issues I've been considering during the past weeks. It's quite exciting and I recommend a peek.
Subscribe to:
Posts (Atom)