I'm using this last post to link to a couple of the documents I've created, all of which are living on the wiki.
The first is a Web Site Collection Plan. This draft suggests policies related to archiving web sites within UARMS.
The other is a Web Site Archiving Workflow and General Information document. This outlines a suggested general workflow, instructions on using HTTrack and the NetarchiveSuite Quick Start version, and information related to the crawls I've done toward the end of this semester.
I have no plans to take down the wiki or this blog anytime in the near future, so these documents should be available until further notice.
Tuesday, April 28, 2009
Thursday, April 23, 2009
April 23, 2009
My fellowship practicum ends next Monday, so this may be my last post.
The best news, perhaps of the semester, is that my ibiblio.org contact got Web Curator Tool (WCT) up and running for me. I've been testing different parts of the program, and there are some bugs (I haven't been able to actually run a harvest) but I've gotten a feel for the procedure the software imposes (harvest authorisation -> target creation -> harvest approval -> target instance -> harvest). The interface is definitely more approachable compared with NetarchiveSuite and HTTrack, down to the colorful grains of wheat next to the "Harvester Configuration" box.
It can still feel a little complex, clicking back and forth between harvest authorisation and target, but I think this is due to (1) my lack of experience with the program (2) some lingering bugs and (3) the fact that setting up the authorisations and targets would require more time investment in the beginning than after your staple harvests were configured.
One point about WCT that vexes me is the difficult install. If I was presented with these three tools, without any prior experience, and told to evaluate them based on interface alone, I'd choose WCT above the others in a heartbeat. But ease-of-use balanced against installation tribulations is a harder decision to make. Not being the installer doesn't really alleviate that tension for me, either.
Also, the harvest authorisation feature of WCT would not be an especially useful aspect of the program for archiving UNC sites. This can be done without gaining the creator's permission based on public records law. The HA feature then becomes a superfluous extra step. On the other side of that coin, in the future, if UARMS or another department wishes to expand the scope of their web site archive to other sites for which permission is needed, this feature would become very useful, because it helps keep the temptation to crawl on the sly at bay.
Another feature of WCT that could work to slow or facilitate the workflow is the harvest approval. If you're a lone harvester, getting approval from yourself is just an extra step. But if multiple people are wrangling and suggesting different harvests, this helps portion out the resources.
I can't comment on the harvesting feature, but will do so if we can make it work in the next few days. Testing it has held up the opinion I gave at the end of my poster: right now, HTTrack is a good option for UARMS, but WCT would be a very nice alternative in the (technologically-supported and web-site-archiving-program-developed) future.
The best news, perhaps of the semester, is that my ibiblio.org contact got Web Curator Tool (WCT) up and running for me. I've been testing different parts of the program, and there are some bugs (I haven't been able to actually run a harvest) but I've gotten a feel for the procedure the software imposes (harvest authorisation -> target creation -> harvest approval -> target instance -> harvest). The interface is definitely more approachable compared with NetarchiveSuite and HTTrack, down to the colorful grains of wheat next to the "Harvester Configuration" box.
It can still feel a little complex, clicking back and forth between harvest authorisation and target, but I think this is due to (1) my lack of experience with the program (2) some lingering bugs and (3) the fact that setting up the authorisations and targets would require more time investment in the beginning than after your staple harvests were configured.One point about WCT that vexes me is the difficult install. If I was presented with these three tools, without any prior experience, and told to evaluate them based on interface alone, I'd choose WCT above the others in a heartbeat. But ease-of-use balanced against installation tribulations is a harder decision to make. Not being the installer doesn't really alleviate that tension for me, either.
Also, the harvest authorisation feature of WCT would not be an especially useful aspect of the program for archiving UNC sites. This can be done without gaining the creator's permission based on public records law. The HA feature then becomes a superfluous extra step. On the other side of that coin, in the future, if UARMS or another department wishes to expand the scope of their web site archive to other sites for which permission is needed, this feature would become very useful, because it helps keep the temptation to crawl on the sly at bay.
Another feature of WCT that could work to slow or facilitate the workflow is the harvest approval. If you're a lone harvester, getting approval from yourself is just an extra step. But if multiple people are wrangling and suggesting different harvests, this helps portion out the resources.
I can't comment on the harvesting feature, but will do so if we can make it work in the next few days. Testing it has held up the opinion I gave at the end of my poster: right now, HTTrack is a good option for UARMS, but WCT would be a very nice alternative in the (technologically-supported and web-site-archiving-program-developed) future.
Monday, April 6, 2009
April 6, 2009
I spent last week volunteering for and attending DigCCurr2009 here in Chapel Hill, which was robustly attended by almost 300 people from around the world. It was an informative experience, and as always a nice chance to renew my enthusiasm by seeing that there are others out there working on similar problems and coming up with different paths forward.
On Thursday, I presented my poster. A lot of good questions came my way. As I've mentioned before, this poster describes my work here in UARMS evaluating three open source software tools used for archiving websites. Those tools are HTTrack, NetarchiveSuite, and Web Curator Tool (WCT).
All three tools would be good choices, and scored very high. HTTrack came out on top with a score of 29. WCT was close behind with 28 points. NetarchiveSuite was third, but still had 25 points.
My recommendation, right now, is for UARMS to go with HTTrack (with WCT as runner-up). This was surprising to me, since I had originally considered it to be the least enticing option. It definitely has the fewest features (no metadata assignment, preservation functions, permissions tracking), but it is the simplest to install and run. I suppose, the moral of this story is that your situation and personnel dictate your best software choice. The thoroughbred may not always be the right horse for you. HTTrack will be easiest for any user to pick up and operate without extensive time reading documentation or learning about archiving websites.
On Thursday, I presented my poster. A lot of good questions came my way. As I've mentioned before, this poster describes my work here in UARMS evaluating three open source software tools used for archiving websites. Those tools are HTTrack, NetarchiveSuite, and Web Curator Tool (WCT).
All three tools would be good choices, and scored very high. HTTrack came out on top with a score of 29. WCT was close behind with 28 points. NetarchiveSuite was third, but still had 25 points.
My recommendation, right now, is for UARMS to go with HTTrack (with WCT as runner-up). This was surprising to me, since I had originally considered it to be the least enticing option. It definitely has the fewest features (no metadata assignment, preservation functions, permissions tracking), but it is the simplest to install and run. I suppose, the moral of this story is that your situation and personnel dictate your best software choice. The thoroughbred may not always be the right horse for you. HTTrack will be easiest for any user to pick up and operate without extensive time reading documentation or learning about archiving websites.
Tuesday, March 24, 2009
March 24, 2009
What a lapse in posts! The good news is that I've been busy preparing for the DigCCurr conference and trying to wrap up installation of the last tool to try (Web Curator Tool). Installation and setup of WCT has proven to be the most onerous of all, and beyond my own technological skill. Two new(ish) computers later, though, and things seem closer. I'll keep you posted.
My poster is practically finished. I ended up doing some modification to the rubric I discussed in the last post. I decided to move some of the criteria on documentation and support to their own category, Documentation/Support, because of the importance of having good explanations for how to install and use these tools. In my experience, lack of documentation can be common with open source tools. But when those using the tools are new to the field or to that type of technology, it becomes all the more important.
I changed the order of criteria for Interface. After some more thought, it seemed to me that simply giving access to a GUI (graphical user interface) is less ideal that offering access to a GUI and to the command line. That category was revised to reflect as much.
I also added some additional features, including bandwidth allocation and the ability to make alterations to harvested materials.
I won't post the results here until after DigCCurr 2009, just to keep up the suspense. Being able to test and thoughtfully evaluate a range of tools is surely a luxury for most institutions. I'm glad I have been able to help UNC in this way.
My poster is practically finished. I ended up doing some modification to the rubric I discussed in the last post. I decided to move some of the criteria on documentation and support to their own category, Documentation/Support, because of the importance of having good explanations for how to install and use these tools. In my experience, lack of documentation can be common with open source tools. But when those using the tools are new to the field or to that type of technology, it becomes all the more important.
I changed the order of criteria for Interface. After some more thought, it seemed to me that simply giving access to a GUI (graphical user interface) is less ideal that offering access to a GUI and to the command line. That category was revised to reflect as much.
I also added some additional features, including bandwidth allocation and the ability to make alterations to harvested materials.
I won't post the results here until after DigCCurr 2009, just to keep up the suspense. Being able to test and thoughtfully evaluate a range of tools is surely a luxury for most institutions. I'm glad I have been able to help UNC in this way.
Tuesday, March 3, 2009
March 3, 2009
I've made more headway on my poster, and I thought I'd share in more depth the software evaluation rubric I've come up with. As I mentioned last time, I've come up with three categories of criteria: Ease of Installation/Setup, Ease of Use, and Features. I started doing some research into software evaluation, to try to see if I could find a vetted rubric to use.
In my literature search, I discovered that software evaluation can be an extremely intense process, punctuated by algorithms and equations. I think this type of evaluation actually centers on the code. I also found some information on ISONORM 9241/10, described here. This came closer to what I was looking for, but centered too much on ergonomics and usability of the software dialog. It didn't cover some of the more subjective aspects I wanted to measure. More relevant to my task were books and articles talking about how to perform a needs assessment and then devise a rubric to suit your own requirements. The down side is the subjective nature of the rubric. But in the end, I decided that for the purposes of my fellowship, where no replicable results are needed, this would work best.
So here's the rubric I've developed. (It's on the wiki, so you'll need access to that before it will come up.) The idea is that each tool will be assessed based on the criteria in each of the 3 categories. The numbers that correspond to the criteria for that tool would be added up to a total. The lower the number, the less conducive it would be to use in UARMS at this point in time. I've written out some explanations for some of the criteria below. For instance, here are my definitions of the criteria in the "Available Documentation for Installation" scale:
None: No documentation available
Sparse: Highly technical and brief
Adequate: Easy to read, mimics common install guides, may be out of date
Robust: Up-to-date, includes troubleshooting section
The "Available Documentation for Use" is similar:
None: No documentation available
Sparse: Some online documentation, may be interspersed with installation information
Adequate: Dedicated user's manual
Robust: User's manual plus built-in help
Finally, the "Knowledge Required" section deserves some clarification:
Program Administrator: Requires a program administrator
UNIX Savvy Librarian: Knows basics of a UNIX system
Technology Savvy User: Feels comfortable doing basic troubleshooting on Windows and Mac platforms
Out of the Box: Feels comfortable doing out of the box installations
Again, I know these are subjective. But I've tried to make them as explicit as possible, and also to select the characteristics I feel have the most impact on whether or not a tool might be adopted in the UARMS setting.
In my literature search, I discovered that software evaluation can be an extremely intense process, punctuated by algorithms and equations. I think this type of evaluation actually centers on the code. I also found some information on ISONORM 9241/10, described here. This came closer to what I was looking for, but centered too much on ergonomics and usability of the software dialog. It didn't cover some of the more subjective aspects I wanted to measure. More relevant to my task were books and articles talking about how to perform a needs assessment and then devise a rubric to suit your own requirements. The down side is the subjective nature of the rubric. But in the end, I decided that for the purposes of my fellowship, where no replicable results are needed, this would work best.
So here's the rubric I've developed. (It's on the wiki, so you'll need access to that before it will come up.) The idea is that each tool will be assessed based on the criteria in each of the 3 categories. The numbers that correspond to the criteria for that tool would be added up to a total. The lower the number, the less conducive it would be to use in UARMS at this point in time. I've written out some explanations for some of the criteria below. For instance, here are my definitions of the criteria in the "Available Documentation for Installation" scale:
None: No documentation available
Sparse: Highly technical and brief
Adequate: Easy to read, mimics common install guides, may be out of date
Robust: Up-to-date, includes troubleshooting section
The "Available Documentation for Use" is similar:
None: No documentation available
Sparse: Some online documentation, may be interspersed with installation information
Adequate: Dedicated user's manual
Robust: User's manual plus built-in help
Finally, the "Knowledge Required" section deserves some clarification:
Program Administrator: Requires a program administrator
UNIX Savvy Librarian: Knows basics of a UNIX system
Technology Savvy User: Feels comfortable doing basic troubleshooting on Windows and Mac platforms
Out of the Box: Feels comfortable doing out of the box installations
Again, I know these are subjective. But I've tried to make them as explicit as possible, and also to select the characteristics I feel have the most impact on whether or not a tool might be adopted in the UARMS setting.
Tuesday, February 24, 2009
February 24, 2009
It's past time for another update, and things have been moving along slowly but surely. The most major accomplishment I can report is that I've finished a draft Web Site Collection Plan. I last mentioned this at the end of January. It's based on my assessment of other web site collection policies as well as the Collection Plan template from the Web-at-Risk project. This draft is available here.
Some parts of this policy are incomplete, simply because they will depend on an overarching digital preservation program. Other parts depend on current metadata practices here in Wilson Library that I haven't been able to pin down yet. Of course they're all flexible recommendations. I think it would be a good place to start, and possibly even a document that can be expanded to other collecting areas.
There's also been some headway on the Web Curator Tool (WCT) installation, thanks to help from staff at ibiblio.org. I gather that it is installed, but I could not yet get it to run. I'm sure this is due to my own tenuous knowledge of how to run things in a Unix environment.
Finally, I've been working on my poster presentation for DigCCurr 2009, which is looming on the horizon. The title is "Getting the Tar Off of Our Heels: Moving Forward with Archiving University of North Carolina at Chapel Hill Websites." Since this poster hinges on the successful trial of WCT, I'm hoping that I can get that tool running in some capacity soon. I've decided to develop a rubric for measuring different aspects of the web archiving tools I've trialed. The three facets will be (1) ease of installation/setup (2) ease of use (3) features. I'm trying to find a vetted set of characteristics for evaluating software, but am thus far not having luck. Barring that, the characteristics I have come up with are highly subjective, but hopefully still meaningful.
Some parts of this policy are incomplete, simply because they will depend on an overarching digital preservation program. Other parts depend on current metadata practices here in Wilson Library that I haven't been able to pin down yet. Of course they're all flexible recommendations. I think it would be a good place to start, and possibly even a document that can be expanded to other collecting areas.
There's also been some headway on the Web Curator Tool (WCT) installation, thanks to help from staff at ibiblio.org. I gather that it is installed, but I could not yet get it to run. I'm sure this is due to my own tenuous knowledge of how to run things in a Unix environment.
Finally, I've been working on my poster presentation for DigCCurr 2009, which is looming on the horizon. The title is "Getting the Tar Off of Our Heels: Moving Forward with Archiving University of North Carolina at Chapel Hill Websites." Since this poster hinges on the successful trial of WCT, I'm hoping that I can get that tool running in some capacity soon. I've decided to develop a rubric for measuring different aspects of the web archiving tools I've trialed. The three facets will be (1) ease of installation/setup (2) ease of use (3) features. I'm trying to find a vetted set of characteristics for evaluating software, but am thus far not having luck. Barring that, the characteristics I have come up with are highly subjective, but hopefully still meaningful.
Tuesday, February 10, 2009
February 10, 2009
I've finished my little experiment, as mentioned in the last post. I have to say, it was pretty enlightening, and I'm glad I took the time to do it. (As a side note, when I was almost finished, I suffered a data loss - you would think that a student of digital curation would know better - and had to start over. So, let that be a lesson to me for backing up my own data.) So here's how it went.
K-12 International Outreach Office
Research & Evaluation (OIA)
Program in the Humanities and Human Values (CoAS)
City & Regional Planning
Dean's Office (School of Medicine)
Biochemistry & Biophysics (School of Medicine)
Medical Science Teaching Labs (School of Medicine)
Business & Finance (School of Dentistry)
Human Resources (School of Dentistry)
Student Services (Dept of Maternal & Child Health)
Center for Urban & Regional Studies
Manuscripts Department (Wilson Library)
Conservation (Wilson Library)
Grounds Services (Facilities)
Building Services (Facilities)
Housekeeping (Facilities)
I read each schedule, keeping track of which series were supposed to be transferred to University Archives (I'll call these "UARMS series" here). I then tried to locate each department's associated website, and was able to do so in all cases. Finally, I scoured these sites looking for any records that fall into the UARMS series.
Here's an example, Housekeeping (Facilities) has 6 series whose records are normally transferred to UARMS in paper format. Two of those six, photographs and policies/procedures, can be found on the Housekeeping website. This means that documents that fall into 33% of its UARMS series records types can be found to some degree in digital form on their website.
As anticipated, the website pages ranged widely in depth and type of content. Some were only one page of text, others were numerous pages deep with multiple file types present. Here are the general results of my survey:
- The percentage of UARMS series document types that could be found on the departments' websites ranged from 0% to 67%.
- The average number of those types found on the website across all sites was only 27%.
- The department with the most record-worthy online content was, surprisingly, Grounds Services.
- Many of these departments had scheduled records series in common. The most common were committee and council records (12 out of 16), correspondence (15 out of 16), photographs (12 out of 16), and polices and procedures (13 out of 16). Of these, only photographs were routinely found online (92% of the departments).
- Photographs, policies/procedures, and conference/workshop (conducted) records were the most common types found online.
- Only 10 of these 16 departments had "website records" on their record schedules, even though all had some sort of website.
Academic Affairs Administration (incl Int'l Programs)
CFNC-Pathways
NC in the World (NC Center for Int'l Understanding)
Licensure Office (Academic Affairs)
Research and Sponsored Programs (Academic Affairs)
To compare, here are some more findings:
- The percentage of UARMS series document types that could be found on the departments' websites ranged from 10% to 57%.
- The average number of those types found on the website across all sites was 39%.
- Much more prevalent for these departments were reports (including annual) and publications.
- I am surprised that more information isn't online, especially considering that UNC is a state university. I had expected a lot more online information in the form of events, strategic planning documents, statistics, and meeting records. I was gratified by the fact that the General Administration sites, on average, did have a lot more of this type of information.
- In general, I was also surprised at how little information some of these departments have on their websites, and how out of date some of that information is.
- I am curious about the number of intranets that exist on campus. I found one or two sites that had log in pages, and one that required a log in to view committee minutes, which was a UARMS series. I think/hope that much of the information I mentioned in #1 may in fact be on the intranet instead of the public web.
- Harvesting these websites will pull in a lot fewer documents that qualify as records than I had expected.
Again, my method has some faults. My sample is small compared to the gamut of UNC departments. Even though I chose randomly, many of the departments were from the same school/college. Also, those who have completed schedules probably are more records-aware in the first place, and may, as a result, have more content online. It also probably isn't fair to look for correspondence or some types of personnel records online, even though they are UARMS series. These aren't the types of things people would typically put on a website. Still, if nothing else, scanning through all of these websites in search of records has given me a better idea of what exactly this institution is putting out there and what, eventually, we would pull in.
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!
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.
"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.
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.
Goals:
- What is the current idea of a responsible web archiving strategy, including preservation, metadata, access?
- Work to refine scope - how much do we want to keep/is feasible to keep
- Identify what has been tried, is being tried
- Compare these with UNC's situation (resources/collections)
- Review current policy and procedure
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.
Tuesday, November 25, 2008
November 25, 2008
The American Library Association Association for Library Collections and Technical Services recently held a 3 day email forum on web archiving. I was clued in to this forum by one of the archivists here, and I'm glad I got to lurk a bit. Although the conversation was a little disjointed, and dominated by several respondents, it was interesting and enlightening. I thought I'd put down some of my thoughts here.
I got the impression that many who spoke up on the list were focusing on government documents. This reflects what I've found in the literature - most published accounts of web archiving in the US also seem to target government sites. This makes sense, considering (1) those sites have, what is considered to be, vetted information (2) have information libraries often collect without heavy selection procedures (3) are perceived as more stable than others.
Of those who responded, the most often mentioned service or tool was the Internet Archive's Archive-it. Others include HTTrack, Context Miner, Fedora, OCLC's Web Archives Workbench, and del.icio.us. This forum was also where I learned about Zoetrope (see my November 20 post).
Manual vs. automated harvesting also seemed to be equally represented. Most still feel that curating the materials is the valuable service that librarians can provide over and above a broad approach like that of the Internet Archive.
Although many stated they weren't actually harvesting web content yet, some of those who were mentioned that they have looked for copyright statements on pages and also sought permission to archive. I think that, because so many expressed their newness to this topic, and because of the newness of web archiving in general, this topic hasn't yet gained a critical mass of experience or attention.
Another really interesting thing was the number of respondents who said they're creating MARC records for freely available website resources, without actually harvesting those resources. This really astonishes me. Most cited storage and technological limitations as barriers to harvesting. I understand that the librarians are interested in getting their users as much information as possible, and hope to do so through catalog searches, but with the ephemeral nature of web content, not to mention unstable URLs, I would imagine these links rot quickly and it would be incredibly demanding to maintain. I also wonder if a list on an archivists' listserv would garner different reactions and methods. More interesting was the claim that they only enter "stable" sites. Sort of an oxymoron. From reading between the lines, I gather that these are sites they feel have a lower possibility for changing URL, but I'm not sure. If there's one thing I've learned in my time at SILS (there's more than one thing, but I'll keep it to one for now), it's that digital objects are anything but stable and that it's best to never think of them as such.
On a related note, many also talked about collecting e-books and e-prints versus the entire website. This must be a difficult decision when you're looking at a document that you formerly collected in print, which is now available online. Many still seem to look for the online equivalent of books or pamphlets for pulling into their repositories. Drawing this distinction allows repositories to draw boundaries in the boundary-less web, but it also may mean they're missing valuable information that has been converted to a "non-book" format.
Again, these are just my thoughts and interpretations of the conversations from the forum and shouldn't be taken as a complete synopsis!
I got the impression that many who spoke up on the list were focusing on government documents. This reflects what I've found in the literature - most published accounts of web archiving in the US also seem to target government sites. This makes sense, considering (1) those sites have, what is considered to be, vetted information (2) have information libraries often collect without heavy selection procedures (3) are perceived as more stable than others.
Of those who responded, the most often mentioned service or tool was the Internet Archive's Archive-it. Others include HTTrack, Context Miner, Fedora, OCLC's Web Archives Workbench, and del.icio.us. This forum was also where I learned about Zoetrope (see my November 20 post).
Manual vs. automated harvesting also seemed to be equally represented. Most still feel that curating the materials is the valuable service that librarians can provide over and above a broad approach like that of the Internet Archive.
Although many stated they weren't actually harvesting web content yet, some of those who were mentioned that they have looked for copyright statements on pages and also sought permission to archive. I think that, because so many expressed their newness to this topic, and because of the newness of web archiving in general, this topic hasn't yet gained a critical mass of experience or attention.
Another really interesting thing was the number of respondents who said they're creating MARC records for freely available website resources, without actually harvesting those resources. This really astonishes me. Most cited storage and technological limitations as barriers to harvesting. I understand that the librarians are interested in getting their users as much information as possible, and hope to do so through catalog searches, but with the ephemeral nature of web content, not to mention unstable URLs, I would imagine these links rot quickly and it would be incredibly demanding to maintain. I also wonder if a list on an archivists' listserv would garner different reactions and methods. More interesting was the claim that they only enter "stable" sites. Sort of an oxymoron. From reading between the lines, I gather that these are sites they feel have a lower possibility for changing URL, but I'm not sure. If there's one thing I've learned in my time at SILS (there's more than one thing, but I'll keep it to one for now), it's that digital objects are anything but stable and that it's best to never think of them as such.
On a related note, many also talked about collecting e-books and e-prints versus the entire website. This must be a difficult decision when you're looking at a document that you formerly collected in print, which is now available online. Many still seem to look for the online equivalent of books or pamphlets for pulling into their repositories. Drawing this distinction allows repositories to draw boundaries in the boundary-less web, but it also may mean they're missing valuable information that has been converted to a "non-book" format.
Again, these are just my thoughts and interpretations of the conversations from the forum and shouldn't be taken as a complete synopsis!
Thursday, November 20, 2008
November 20, 2008
Talk about a neat and shiny tool. Julien Masanes forwarded this link to a web archiving listserv I've subscribed to. It is definitely worth the time to watch the video:
http://uwnews.washington.edu/ni/article.asp?articleID=45255
Zoetrope looks like a fascinating way to actually access harvested web material. Developed by University of Washington and Adobe, it allows you to compare a page over time, multiple pages over time, or even sections of multiple pages (using "lenses") over time. It will even graph changes in a numerical entity (think product prices or temperatures). Although it harvests sites VERY often, I would hope it would still be useful for a site harvested only monthly or bimonthly. They mention eventually using the Internet Archive as a source for harvested sites, which may mean it can read and display .arc files. Even better - they plan to make it available for free.
http://uwnews.washington.edu/ni/article.asp?articleID=45255
Zoetrope looks like a fascinating way to actually access harvested web material. Developed by University of Washington and Adobe, it allows you to compare a page over time, multiple pages over time, or even sections of multiple pages (using "lenses") over time. It will even graph changes in a numerical entity (think product prices or temperatures). Although it harvests sites VERY often, I would hope it would still be useful for a site harvested only monthly or bimonthly. They mention eventually using the Internet Archive as a source for harvested sites, which may mean it can read and display .arc files. Even better - they plan to make it available for free.
Monday, November 10, 2008
November 10, 2008
I am not a system administrator.
This is a really hard admission for me to make. I've been struggling to try to wrap my head around installing some web archiving utilities, like Netarchive Suite and WERA. Thanks to the generous help of ibiblio.org folks, the first tool is now up and running (albeit in a trial version) on our test server and I've completed my first harvest. I'm really excited about that major hurdle. Now, I just need to get a viewer for the .arc files created by Netarchive Suite.
I've had to admit that, despite my open mind and eagerness to tackle these things myself, I simply do not have the technological background to strike out on my own. This hit home when I was sitting down with an ibiblio.org staff member, who deftly and quickly took care of an issue I had been struggling with for over a week. I've been trying to figure out why this bothers me so much. Perhaps its because I've never really met with something within the scope of a job that was so far beyond my skill level that I knew I couldn't just bootstrap myself up. Maybe it's because everyone seems to need IT support, in low supply, and this project will undoubtedly fall to the bottom of the stack. Or maybe it's knowing that, without installation of these tools, I'm stuck. I can't go tackle a different set of boxes.
My frustration in part comes from the fact that installation instructions for the full version of Netarchive Suite, or the Web Curator Tool, or even WERA, are all written for a system administrator. Even the user manuals often state "your system administrator will do X..." The set of skills that these documents assume is already beyond what I have. It's a matter of encountering one term, only to be met with multiple other terms that I'm unfamiliar with.
This has been an eye-opening experience. Despite the fact that I feel pretty comfortable and familiar with technology, there is an entire realm of technological depth that supports a lot of the open source tools many librarians and archivists are advocating. To use these tools, I cannot operate without system administrator support. Period.
This is a really hard admission for me to make. I've been struggling to try to wrap my head around installing some web archiving utilities, like Netarchive Suite and WERA. Thanks to the generous help of ibiblio.org folks, the first tool is now up and running (albeit in a trial version) on our test server and I've completed my first harvest. I'm really excited about that major hurdle. Now, I just need to get a viewer for the .arc files created by Netarchive Suite.
I've had to admit that, despite my open mind and eagerness to tackle these things myself, I simply do not have the technological background to strike out on my own. This hit home when I was sitting down with an ibiblio.org staff member, who deftly and quickly took care of an issue I had been struggling with for over a week. I've been trying to figure out why this bothers me so much. Perhaps its because I've never really met with something within the scope of a job that was so far beyond my skill level that I knew I couldn't just bootstrap myself up. Maybe it's because everyone seems to need IT support, in low supply, and this project will undoubtedly fall to the bottom of the stack. Or maybe it's knowing that, without installation of these tools, I'm stuck. I can't go tackle a different set of boxes.
My frustration in part comes from the fact that installation instructions for the full version of Netarchive Suite, or the Web Curator Tool, or even WERA, are all written for a system administrator. Even the user manuals often state "your system administrator will do X..." The set of skills that these documents assume is already beyond what I have. It's a matter of encountering one term, only to be met with multiple other terms that I'm unfamiliar with.
This has been an eye-opening experience. Despite the fact that I feel pretty comfortable and familiar with technology, there is an entire realm of technological depth that supports a lot of the open source tools many librarians and archivists are advocating. To use these tools, I cannot operate without system administrator support. Period.
Friday, October 24, 2008
October 24, 2008
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.
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.
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.
Monday, September 29, 2008
September 29, 2008
Tool investigation continues! After contacting Paul Koerbin at the NLA and receiving a quick and informative response, I've learned that PANDAS is not being offered broadly as an open source solution for other institutions. This is primarily due to resource constraints and the fact that several other good open source tools are available. Paul suggested the Web Curator Tool (WCT) and also the Netarchive Suite (NAS), both of which were listed in my previous blog.
Looking at the possible implementation of these two tools, I've discovered to my dismay that I can't forge ahead on my own. System administrators will be required both for server installation and/or setting up a Linux box. It also makes me realize that, even if I had all of the technological knowhow to understand the installation requirements, someone with knowledge of the system in place here would still need to lend me their time and talents. This really highlights the fact that collaboration with IT is more and more necessary. I can see why librarians and archivists might get nervous at this dependence on an external department. It requires trust and patience.
Looking at the possible implementation of these two tools, I've discovered to my dismay that I can't forge ahead on my own. System administrators will be required both for server installation and/or setting up a Linux box. It also makes me realize that, even if I had all of the technological knowhow to understand the installation requirements, someone with knowledge of the system in place here would still need to lend me their time and talents. This really highlights the fact that collaboration with IT is more and more necessary. I can see why librarians and archivists might get nervous at this dependence on an external department. It requires trust and patience.
Thursday, September 25, 2008
September 26, 2008
One of the ways I've come to categorize tools is by "accessibility for non-technical users." Of the web archiving tools I've looked at, I would rate them in the following way, from most accessible to least accessible.
- Archive-It (Internet Archive) (discussed in the previous post)
- WCT - Web Curator Tool (National Library of New Zealand + British Library)
- PANDAS - PANDORA Digital Archiving System (National Library of Australia)
- Web Archives Workbench (OCLC)
- Netarchive Suite (Danish Royal Library and State and University Library)
- IIPC Toolkit (a group of separate tools like Heritrix and DeepArc)
September 25, 2008
This week I have been looking at some of the tools available for archiving websites. These include tools which address part of the entire archiving process like HTTrack (an offline browser that can be used to harvest site) and AONS (an "automatic obsolescence notification system" that checks file format registries against the files in your collection, notifying you when some are in danger of going defunct). There are also multi-function tools that can perform multiple tasks. The elusive Web Archived Workbench from OCLC is one of these, although there is very little OCLC-sponsored documentation regarding this software online. You're welcome to see my annotated list of these and other tools at the wiki.
The Internet Archive's "Archive-it" is another example of a multi-function tool. This is a fee-based service, although I couldn't find any specific pricing structure. If you subscribe to the service, you can use Archive-it to schedule and scope your harvests. Unlike the general Wayback Machine web crawls, Archive-it users can create collections of their web resources (the common complaint about the Wayback Machine is the access method, which is solely through full-text search or known-URL selection). The Internet Archive hosts and stores your data, and if you terminate your agreement it will keep the information, adding it into its general web collection. A number of university entities are taking advantage of the IA's services, including the Carolina Center for the Study of the Middle East and Muslim Civilizations here at UNC. Among our peers, the University of Southern California, the Latin American Information Network at UT-Austin, and the Stem Cell Research Project at UW-Madison are also IA partners. There is definitely an attraction to having an already developed and technologically accessible alternative, but there are also several possible downsides:
The Internet Archive's "Archive-it" is another example of a multi-function tool. This is a fee-based service, although I couldn't find any specific pricing structure. If you subscribe to the service, you can use Archive-it to schedule and scope your harvests. Unlike the general Wayback Machine web crawls, Archive-it users can create collections of their web resources (the common complaint about the Wayback Machine is the access method, which is solely through full-text search or known-URL selection). The Internet Archive hosts and stores your data, and if you terminate your agreement it will keep the information, adding it into its general web collection. A number of university entities are taking advantage of the IA's services, including the Carolina Center for the Study of the Middle East and Muslim Civilizations here at UNC. Among our peers, the University of Southern California, the Latin American Information Network at UT-Austin, and the Stem Cell Research Project at UW-Madison are also IA partners. There is definitely an attraction to having an already developed and technologically accessible alternative, but there are also several possible downsides:
- This is a for-fee service.
- The IA crawl is still only a "snapshot." Accessing deep and dynamic information isn't part of this picture.
- Although the IA has dispersed redundant storage, you are still placing the stewardship of your materials into the hands of another agency.
- All IA materials are public. The site mentions that you can make materials private by contacting the IA for a special arrangement. There's no mention if selected materials can be made private, or if it's an all-or-nothing deal. Again, this is another area in which control will have to be handed over to an external agency.
In a sense, this boils down to the general debate over using your own solutions vs. outsourcing. Although the IA does give you autonomy over collecting and organizing, you're still beholden to their technological and business changes. Based on my general observations and investigations, it seems that more universities are choosing the IA option at this point in time. Whether or not they are exploring in-house alternatives as well is less clear to me.
Thursday, September 18, 2008
September 18, 2008
I've unearthed another university that, through partnerships, has been working on archiving websites. Although it is not considered a peer of UNC, given the very few universities that are far enough along with web archiving to have incorporated it into their online presence (and, by few, I mean one), I decided that the University of North Texas Libraries definitely deserves note.
I discovered their efforts because they're a member of the IIPC - the only university in the current list of North American members. Their rather morbidly named CyberCemetery "provides permanent public access to the websites and publications of defunct U.S. government agencies and commissions." ("Permanent" - very ambitious) In addition to searching the site, you can browse by agency, date of expiration or branch of government. The browsable links I clicked were broken due to a recent system change, but the search mechanism seems to work fine. Sites come up with a simple, small textual header of "Archive." It's a straightforward, easy to navigate system.
According to the IA's Web Archiving Blog, I found out that UNT will be archiving the end-of-term presidential websites, partnering with the following acronym parade: IA, CDL, the LoC, and the USGPO.
It's interesting to me that UNT hasn't made archives of their own website available, but is focusing on external government sites. UMich will have to be the closest model for archiving our own sites, for now.
I discovered their efforts because they're a member of the IIPC - the only university in the current list of North American members. Their rather morbidly named CyberCemetery "provides permanent public access to the websites and publications of defunct U.S. government agencies and commissions." ("Permanent" - very ambitious) In addition to searching the site, you can browse by agency, date of expiration or branch of government. The browsable links I clicked were broken due to a recent system change, but the search mechanism seems to work fine. Sites come up with a simple, small textual header of "Archive." It's a straightforward, easy to navigate system.
According to the IA's Web Archiving Blog, I found out that UNT will be archiving the end-of-term presidential websites, partnering with the following acronym parade: IA, CDL, the LoC, and the USGPO.
It's interesting to me that UNT hasn't made archives of their own website available, but is focusing on external government sites. UMich will have to be the closest model for archiving our own sites, for now.
Subscribe to:
Posts (Atom)