The Beginning Drupal class on November 20 went well. We had about 25 attendees, and aside from the fact that the Internet connection was a little problematic in our classroom, there were no major snafus. I'm now moving on to the second class, which is officially on the calender for Dec. 4th. There are a number of people from the first class who have already signed on for the second one. With the first class under my belt, planning the next one should be less work. I'm actually rather enjoying the process, especially the feeling that I'm helping facilitate a community around campus. The interest is out there; all that's needed is a little organization to get things off the ground, and people seem genuinely grateful for the opportunity to get training.
Last week I also made progress on the Portal Community Interface template. After messing around with Drupal all semester, I realized I'd finally gotten to the point that I feel like I know what I'm doing when I use it. I'm hardly an expert, but I don't have to spend a lot of time figuring out how to do basic things anymore, which is satisfying. I still have more work to do on the CPI template, but I think I should have a good working draft by the end of next week.
Friday, November 28, 2008
Sunday, November 16, 2008
Week 12: Event Coordination
Last weekend I was at the Midwest Archives Conference symposium on digital preservation in Lawrence, KS, which means I once again have two weeks worth of blogging to catch up on. And once again, it was a busy two weeks. Before leaving town on Thursday the 6th, I was scrambling to get ready for our consultant's visit the following week. This involved finding available space on campus to hold two public presentations, one on Tuesday evening and another on Wednesday morning; sending out last minute emails to advertise the events; getting information for a press release; and having a conference call with David (the consultant from CTC).
It was a little crazy, but everything turned out fine. Unfortunately I couldn't attend the Tuesday presentation on building digital communities because I had class, but I heard it was well-attended. On Wednesday morning, we had a two-hour consulting session to talk about the Community Information Portal, which I thought went really well. Then came the second presentation, which was about Drupal modules and drew an even bigger crowd than the previous night's. All in all, I thought the visit was a success.
I couldn't rest on my laurels though, because I still had the Nov. 20 Drupal class to finish coordinating. This took up a good deal of my time last week. Almost 30 people are expected to attend, and I've been fielding emails from them. Cliff and Matt Arant will be leading the class, and we had a meeting on Thursday to plan the course. Since the first class is covering basic Drupal skills, we also decided to follow up with a second, more advanced class on site building in December. This will be taught by Daniel Walls, a student in the Engineering Department. So now I've begun planning that as well, and will simultaneously need to organize the 2-day training workshop we're planning for December or January.
Somewhere in there I also need to work on the Portal Community Interface (not to be confused with the Community Information Portal), but that's a topic for another post. Hopefully I will have some progress to report on that next time.
It was a little crazy, but everything turned out fine. Unfortunately I couldn't attend the Tuesday presentation on building digital communities because I had class, but I heard it was well-attended. On Wednesday morning, we had a two-hour consulting session to talk about the Community Information Portal, which I thought went really well. Then came the second presentation, which was about Drupal modules and drew an even bigger crowd than the previous night's. All in all, I thought the visit was a success.
I couldn't rest on my laurels though, because I still had the Nov. 20 Drupal class to finish coordinating. This took up a good deal of my time last week. Almost 30 people are expected to attend, and I've been fielding emails from them. Cliff and Matt Arant will be leading the class, and we had a meeting on Thursday to plan the course. Since the first class is covering basic Drupal skills, we also decided to follow up with a second, more advanced class on site building in December. This will be taught by Daniel Walls, a student in the Engineering Department. So now I've begun planning that as well, and will simultaneously need to organize the 2-day training workshop we're planning for December or January.
Somewhere in there I also need to work on the Portal Community Interface (not to be confused with the Community Information Portal), but that's a topic for another post. Hopefully I will have some progress to report on that next time.
Sunday, November 2, 2008
Week 10: A List
The last couple of weeks have been pretty busy, therefore I'm going to make things easier by briefly listing what I've been up to:
- didn't go to DrupalCamp in Chicago (too much other work to do that weekend);
- scheduled a pre-training Drupal basics class in the Information Arcade for Nov. 20;
- found some potential volunteers (grad students in the Engineering dept.) to teach the class with Cliff;
- spoke more with Chicago Technology Cooperative about having them come to Iowa City to conduct the 2-day training in early-mid December (still working on the logistics);
- also discussed having one of the CTC people come to the WiderNet office to consult on the CIP project, tentatively scheduled for Nov. 10 or 11 but yet to be finalized;
- posted an ad on www.rentacoder.com for someone to develop the CIP site-builder interface, also sent CTC specifications for the interface and got a REALLY high price quote (I'll be talking with Cliff and them about it more next week);
- was contacted by someone with an organization similar to CTC called Net2Community, who is working on a somewhat similar project, and scheduled a call with him for next week to discuss potential collaboration;
- started a new people directory template in Drupal;
- did a fresh Drupal installation so the database can be copied and used for future templates;
- worked on installing and using some new modules.
Wednesday, October 22, 2008
Week 8: New Collaborations
Last week Cliff and I spoke with the Chicago Technology Cooperative, whom I mentioned in my previous post. They said they liked the sounds of our project and are interested in collaborating with us, so we talked about how that might happen. They indicated they would be able to come to Iowa City to conduct a Drupal training, and since they cater to nonprofits their rates are fairly reasonable, so we are pursuing that option. They may also consult with us remotely on development of the CIP portal. I'm glad we happened to stumble upon their website.
I also met with Jim Elmborg this week to discuss Drupal and getting SLIS involved in the training. He offered to help with planning, funding, and recruiting attendees from other departments, which will be a big help and gets us one step closer to getting the training off the ground.
Cliff and I have also been discussing driving to Chicago for Drupal Camp, which is a conference being held Oct. 24-25. I've emailed other staff at Widernet to see if we could get a group together and take a university van. It's a big maybe, but it would be a good way to learn about Drupal and network with the Drupal community (as well as meet the Chicago Tech people, who will be attending).
I also met with Jim Elmborg this week to discuss Drupal and getting SLIS involved in the training. He offered to help with planning, funding, and recruiting attendees from other departments, which will be a big help and gets us one step closer to getting the training off the ground.
Cliff and I have also been discussing driving to Chicago for Drupal Camp, which is a conference being held Oct. 24-25. I've emailed other staff at Widernet to see if we could get a group together and take a university van. It's a big maybe, but it would be a good way to learn about Drupal and network with the Drupal community (as well as meet the Chicago Tech people, who will be attending).
Wednesday, October 15, 2008
Week 7: Workshop Planning
I'm a little late posting about last week's goings-on. During the beginning of the week, I spent a lot of time in Drupal configuring views and user permissions for the sample template. I presented this to Cliff in a meeting on Thursday and got feedback about what changes could be made. Overall I felt like I had made a lot of progress with that part of the project. I also started documenting what I'm learning about Drupal and how I've used it to create the template.
Following that meeting, we had another one with Tom Burns and Mark Hale from ITS. We talked about getting a Drupal training organized and agreed on next steps for accomplishing this. Tom was going to contact Matt Westgate from Lullabot to follow up on a potential training over Thanksgiving break. He also volunteered to send out a survey on the U of I developer's website he runs, to gauge interest. Mark offered to investigate room reservations and funding possibilities.
I felt like we really got the ball rolling on making the Drupal workshop a reality, and it was satisfying that our plans were starting to take shape. The meeting also led to a couple of breakthroughs. First, we stumbled upon a website for the Chicago Technology Cooperative, which conducts Drupal trainings for non-profits. I sent them an email afterward to inquire about the possibility of consulting with them on the project. Second, the meeting gave me the idea that SLIS could be involved with the training. I emailed Jim and Padmini proposing that SLIS students might want to attend, and received enthusiastic responses, including offers of funding to support the event.
The collaborations I've been working to foster for the last month or so are starting to come together, and I think we're gaining momentum. The important thing now will be to keep people interested/excited in the training.
Following that meeting, we had another one with Tom Burns and Mark Hale from ITS. We talked about getting a Drupal training organized and agreed on next steps for accomplishing this. Tom was going to contact Matt Westgate from Lullabot to follow up on a potential training over Thanksgiving break. He also volunteered to send out a survey on the U of I developer's website he runs, to gauge interest. Mark offered to investigate room reservations and funding possibilities.
I felt like we really got the ball rolling on making the Drupal workshop a reality, and it was satisfying that our plans were starting to take shape. The meeting also led to a couple of breakthroughs. First, we stumbled upon a website for the Chicago Technology Cooperative, which conducts Drupal trainings for non-profits. I sent them an email afterward to inquire about the possibility of consulting with them on the project. Second, the meeting gave me the idea that SLIS could be involved with the training. I emailed Jim and Padmini proposing that SLIS students might want to attend, and received enthusiastic responses, including offers of funding to support the event.
The collaborations I've been working to foster for the last month or so are starting to come together, and I think we're gaining momentum. The important thing now will be to keep people interested/excited in the training.
Monday, October 6, 2008
Week 6: Odds 'n Ends
Just a quick recap of last week: I sent out a few more emails to possible collaborators, but have gotten limited responses. That part of the project seems to have stalled. I'm still trying to set up a meeting with Tom Burns and Cliff to talk about organizing a Drupal training. I worked on project documentation, and spent more time online looking at design templates. I downloaded Elgg, the open-source social networking software, but was unsuccessful in completing the installation. I also worked on finalizing the list of fields to be included in the CIP templates.
My triumph for the week was finally figurung out how Views works in Drupal. This will let us create customized lists of content, so that each time a content provider adds a new entry to a directory, it will automatically be filtered for the list in that category. I still have some tweaking to do, but at least now I understand how it works.
This week, I'll be putting an ad up on the Rentacoder.com site so we can hopefully hire someone to create the user interface. Also will be continuing with the previously mentioned tasks, and whatever else happens to come up.
My triumph for the week was finally figurung out how Views works in Drupal. This will let us create customized lists of content, so that each time a content provider adds a new entry to a directory, it will automatically be filtered for the list in that category. I still have some tweaking to do, but at least now I understand how it works.
This week, I'll be putting an ad up on the Rentacoder.com site so we can hopefully hire someone to create the user interface. Also will be continuing with the previously mentioned tasks, and whatever else happens to come up.
Saturday, September 27, 2008
Week 5: Networking
This week I focused on trying to locate the Drupal community in Iowa, in the hopes of getting people to help us execute the project. I contacted a "virtual" company, Lullabot, that specializes in training people in Drupal; Cliff and I spoke with them and there is a possibility they may do some training for us in November. I also found an Iowa users group on the Drupal groups website and put up a post asking for help. I was invited to their monthly meeting next week in Ames, but am unable to attend. The responses I got did show interest in the project, so I'm hoping I can figure out a way to work with them.
I also contacted an instructor in the Art department about the possibility of arranging for design students to "donate" templates for the interface. I emailed my Electronic Publishing instructor from last spring to ask his advice, and I also found a person in the ITS department who is a Drupal enthusiast and is involved in the developer community on campus. Cliff and I will be meeting with him, hopefully next week (incidentally, this led me to discover that there will be a "Code Camp" in Des Moines in November, which might be a good place to learn about Drupal and meet collaborators). Finally, I emailed Bharani, the new tech support person for the digital fellows, to see if she might also be a resource on the project.
So I basically have a lot of balls up in the air right now, and it will take some time for them to lead to anything concrete, but I feel like I've made progress. The challenge will be to get people who say they're interested in the project, to actually commit to working on it -- especially if it's on a volunteer basis.
Other things on my plate: looking for sample interfaces -- mostly site builders, which is pretty much the functionality we want. I especially like Google Sites and Weebly; they both have clean, uncluttered design and user-friendly interfaces. I'm also working on making a web page for the CIP project on the Widernet website, as an informational tool for people who may be interested in working on it. Also, I'm narrowing down the possible features and functions that we will want to include in each template.
I also contacted an instructor in the Art department about the possibility of arranging for design students to "donate" templates for the interface. I emailed my Electronic Publishing instructor from last spring to ask his advice, and I also found a person in the ITS department who is a Drupal enthusiast and is involved in the developer community on campus. Cliff and I will be meeting with him, hopefully next week (incidentally, this led me to discover that there will be a "Code Camp" in Des Moines in November, which might be a good place to learn about Drupal and meet collaborators). Finally, I emailed Bharani, the new tech support person for the digital fellows, to see if she might also be a resource on the project.
So I basically have a lot of balls up in the air right now, and it will take some time for them to lead to anything concrete, but I feel like I've made progress. The challenge will be to get people who say they're interested in the project, to actually commit to working on it -- especially if it's on a volunteer basis.
Other things on my plate: looking for sample interfaces -- mostly site builders, which is pretty much the functionality we want. I especially like Google Sites and Weebly; they both have clean, uncluttered design and user-friendly interfaces. I'm also working on making a web page for the CIP project on the Widernet website, as an informational tool for people who may be interested in working on it. Also, I'm narrowing down the possible features and functions that we will want to include in each template.
Saturday, September 20, 2008
Week 4: Changing Gears
This week threw me for a loop. During a meeting on Thursday, I found out that I really didn't need to be spending time figuring out how to make things work in Drupal, or any other CMS for that matter. We will hire "rent-a-coders" to customize the CMS once we have decided what features we want. My involvement is to research what those features should be, and to guide the process of making the whole thing happen. My role is purely project management and not really hands-on as far as implementing the site, which I hadn't been entirely clear on before.
It was decided in the meeting that we will be using Drupal for sure. The interface for users to add their own content should be "dirt easy", meaning users shouldn't have to log in or use the CMS back-end at all, which isn't possible with Drupal as it is (at least, not that I can tell). So the coders we hire will be be in charge of making this possible. My job now is to research the Drupal community in Iowa and elsewhere and find people we can approach about doing this for us, and/or coming in and training people in the office on using Drupal. I will find people to design the interface; Cliff mentioned design students at the U of I as a possibility as they have volunteered their services before. I will also be in touch with Widernet contacts in Africa who will help us decide on what features should be included, as well as adding local content to the demo version that will be shown to Intel in December or January.
So far, I've put in an inquiry with a Drupal consulting and development business that has an associate in Ames, to see if they can help us out. With the Intel grant, we can afford to pay outside people, although I need to find out for sure what our budget is for that. I also found a group of Drupal enthusiasts in Iowa, and I plan to post a message to their group site next week. Next week I will work further on getting in contact with other people who we can use on the project.
It was decided in the meeting that we will be using Drupal for sure. The interface for users to add their own content should be "dirt easy", meaning users shouldn't have to log in or use the CMS back-end at all, which isn't possible with Drupal as it is (at least, not that I can tell). So the coders we hire will be be in charge of making this possible. My job now is to research the Drupal community in Iowa and elsewhere and find people we can approach about doing this for us, and/or coming in and training people in the office on using Drupal. I will find people to design the interface; Cliff mentioned design students at the U of I as a possibility as they have volunteered their services before. I will also be in touch with Widernet contacts in Africa who will help us decide on what features should be included, as well as adding local content to the demo version that will be shown to Intel in December or January.
So far, I've put in an inquiry with a Drupal consulting and development business that has an associate in Ames, to see if they can help us out. With the Intel grant, we can afford to pay outside people, although I need to find out for sure what our budget is for that. I also found a group of Drupal enthusiasts in Iowa, and I plan to post a message to their group site next week. Next week I will work further on getting in contact with other people who we can use on the project.
Sunday, September 14, 2008
Week 3: Not Quite Sure What I'm Doing Yet...
This week saw less progress than usual due to an illness, which left me missing two days of work. I also had three meetings over the course of the week, so I wasn't left with a lot of time to do project work. I basically continued with what I had been working on last week - experimenting with Drupal and Site@School. On Friday we had Drupal "expert" Matt Arant come in and walk the whole staff through the basics of Drupal, since the Widernet website is being migrated. Matt and I are going to meet next week so he can talk with me about how Drupal can be used to create a user-customized template.
I have a general idea of how this can be done, but the specifics are still sort of eluding me. For example, will each user of the eGranary have to create an account in the CMS in order to change the template, or just use the administrator account? How might the fact that it will be housed on a local server make using it different? I also added the Drupal module that let's the administrator create customized fields for users to populate, but it seems pretty complicated and I'm not having a lot of success figuring it out on my own. I'm hoping Matt can show me how to do it.
I also spent some time investigating other CMS's that we could use. One possibility I found was called EZPublish, which has a very intuitive-looking user interface. I don't have it installed yet but will probably give it a test run next week. Since I'm also familiar with Joomla (I used it for a group project in Electronic Publishing last spring), I'm thinking I should see how it would compare to Drupal as far as meeting the needs of the project.
Next week I'll work on these things and hopefully get more done!
I have a general idea of how this can be done, but the specifics are still sort of eluding me. For example, will each user of the eGranary have to create an account in the CMS in order to change the template, or just use the administrator account? How might the fact that it will be housed on a local server make using it different? I also added the Drupal module that let's the administrator create customized fields for users to populate, but it seems pretty complicated and I'm not having a lot of success figuring it out on my own. I'm hoping Matt can show me how to do it.
I also spent some time investigating other CMS's that we could use. One possibility I found was called EZPublish, which has a very intuitive-looking user interface. I don't have it installed yet but will probably give it a test run next week. Since I'm also familiar with Joomla (I used it for a group project in Electronic Publishing last spring), I'm thinking I should see how it would compare to Drupal as far as meeting the needs of the project.
Next week I'll work on these things and hopefully get more done!
Sunday, September 7, 2008
Week 2: Lots of Time in the Server Room
The week started off with a meeting between myself and Brent to talk more about the project. The need is for one or more templates that can be used by various community groups, e.g. schools, health clinics, etc., to create their own web pages or sites. My job during the first couple of weeks is to research various content management systems and try to determine which one/s would work best, as well as looking at existing websites of this type to see what information is commonly included.
I checked out some elementary school web sites, and found their basic content to be fairly uniform (contact info, academic calendars, faculty lists, and lunch menus are typical). I also looked at an open-source CMS specifically geared toward primary schools, called Site@School. It provides templates for schools to create and maintain their own sites for free. I installed it on the WiderNet server so I can try it out. At first glance, it looks like a good option.
The rest of the week I spent tackling Drupal. After getting it installed on the server (which was a bit tricky, but helped me brush up on my rusty command line and SQL skills), I played around and tried to figure out how it can meet our needs. There are a ton of modules to download, and I added a few that seem useful. I also did more reading and watched some online tutorials. My feeling is that Drupal can be used to do just about anything, but that very fact gives it a steep learning curve. I have a feeling I won't fully understand how it works until I have a concrete draft of the template to plug in. But it will help that WiderNet is going to start using Drupal for its website, and will be bringing in an "expert" this week to teach staff the basics.
In the coming week, I will begin working with Site at School and look around for other CMS's we might be able to use. I also need to get started on another ongoing task, which is to create documentation for the project.
I checked out some elementary school web sites, and found their basic content to be fairly uniform (contact info, academic calendars, faculty lists, and lunch menus are typical). I also looked at an open-source CMS specifically geared toward primary schools, called Site@School. It provides templates for schools to create and maintain their own sites for free. I installed it on the WiderNet server so I can try it out. At first glance, it looks like a good option.
The rest of the week I spent tackling Drupal. After getting it installed on the server (which was a bit tricky, but helped me brush up on my rusty command line and SQL skills), I played around and tried to figure out how it can meet our needs. There are a ton of modules to download, and I added a few that seem useful. I also did more reading and watched some online tutorials. My feeling is that Drupal can be used to do just about anything, but that very fact gives it a steep learning curve. I have a feeling I won't fully understand how it works until I have a concrete draft of the template to plug in. But it will help that WiderNet is going to start using Drupal for its website, and will be bringing in an "expert" this week to teach staff the basics.
In the coming week, I will begin working with Site at School and look around for other CMS's we might be able to use. I also need to get started on another ongoing task, which is to create documentation for the project.
Friday, August 29, 2008
Summer Recap and Semester Preview
I didn't blog this summer, though I did continue to do project work in DLS. I was officially still on the EAD "task force", which in my case involved attending the occasional meeting to keep up on the project's progress. There wasn't as much for Joanna and I to do during this time, as the main tasks fell to John (working with the Archon database) and Raj (creating the web interface). There's a day trip planned to the University of Illinois in the next couple of weeks to meet with the Archon developers, but since my involvement at this point is minimal I likely won't go. I do plan to continue going to task force meetings this semester, just to stay informed and help with anything that might be needed.
My focus this summer was on migrating the Virtual Writing University audio files into the Iowa Digital Library. I migrated two sub-collections within the VWU digital collection, which were recordings from the 2005 NonfictioNow Conference and interviews by Prof. Peter Nazareth with members of the International Writing Program (around 100 files in all). The project involved reformatting the files from wav to mp3, uploading them to contentDM, making a metadata template, creating the records, and coming up with a preliminary interface design. As a former comparative literature major, it was really interesting for me to listen to the recordings and research the writers involved in order to catalog the entries. There are more subcollections to be added and the interface to be fleshed out, which will be continued this semester by a new set of fellows.
This semester, my last, I will be working on the eGranary Digital Library at Widernet. While I'll miss DLS, it will be good to get some experience in a different setting. This week I met with Cliff Missen and Brent Palmer, my new mentors, to discuss project possibilities. We decided I will start out working to develop the template for a "community information platform", which will allow users of the eGranary to add their own content (for creating local directories, etc.). Widernet is partnering with Intel, which donated a large sum of many for the project, so it looks to be an interesting opportunity. In fact, the day after our meeting Cliff and Brent left for California to meet with the Intel folks.
I spent the rest of the week familiarizing myself with the eGranary and researching Drupal, the content management system we will use to create the template. While I haven't used Drupal before, the fact that I learned Joomla! in Electronic Publishing last semester will give me a big leg up. Next week, I'll meet with Brent to learn more about the project and discuss next steps.
My focus this summer was on migrating the Virtual Writing University audio files into the Iowa Digital Library. I migrated two sub-collections within the VWU digital collection, which were recordings from the 2005 NonfictioNow Conference and interviews by Prof. Peter Nazareth with members of the International Writing Program (around 100 files in all). The project involved reformatting the files from wav to mp3, uploading them to contentDM, making a metadata template, creating the records, and coming up with a preliminary interface design. As a former comparative literature major, it was really interesting for me to listen to the recordings and research the writers involved in order to catalog the entries. There are more subcollections to be added and the interface to be fleshed out, which will be continued this semester by a new set of fellows.
This semester, my last, I will be working on the eGranary Digital Library at Widernet. While I'll miss DLS, it will be good to get some experience in a different setting. This week I met with Cliff Missen and Brent Palmer, my new mentors, to discuss project possibilities. We decided I will start out working to develop the template for a "community information platform", which will allow users of the eGranary to add their own content (for creating local directories, etc.). Widernet is partnering with Intel, which donated a large sum of many for the project, so it looks to be an interesting opportunity. In fact, the day after our meeting Cliff and Brent left for California to meet with the Intel folks.
I spent the rest of the week familiarizing myself with the eGranary and researching Drupal, the content management system we will use to create the template. While I haven't used Drupal before, the fact that I learned Joomla! in Electronic Publishing last semester will give me a big leg up. Next week, I'll meet with Brent to learn more about the project and discuss next steps.
Saturday, April 26, 2008
Week 10-11: Troubleshooting Archon
I've been a bit remiss about keeping up on the weekly postings. This is partly because school has gotten incredibly busy, and partly because progress on the EAD project is rather slow going so I don't have a lot of regular updates to make.
As I mentioned in a previous post, we ran into trouble importing our XML files into Archon -- basically, it seems it can't be done. We were hoping this would be easily fixed, but it has turned into a significant issue (or at least, a time-consuming one). John Osborn has been diligently trying to figure out a way to work around the problem, which so far involves converting the EAD into delimited files, importing those into Archon, then exporting them as EAD (I hope I've got that right -- it's a little confusing). It's a roundabout method to accomplish what should be a straightforward task, which Archon is supposed to be able to handle. There's obviously some glitch happening, but we don't know for sure what it is.
In searching online, I haven't found as much documentation as I'd hoped about how others have implemented Archon. I did read a blog post written by a librarian who had the same problem with importing XML files, although I haven't found any information indicating the cause or solution. The main task for the remainder of the semester may well be trying to figure this out.
We've been having meetings with Jen, John, Sue, Linda, and a new apps person, Raj, to discuss the import issue and the search interface design. The meetings are great experience because they give Joanna and I an inside view of how project management and workflow actually happen on the job. I feel less like a student worker than a professional and team member, which is a good feeling.
In addition, we've also been continuing to encode finding aids for the sample set using our template. After much debate about how to handle the intellectual hierarchy of the container lists, which can be hard to discern from the finding aids, we decided to simplify it as much as possible. This means not specifying levels like series, subseries or folder, and just using numbered container tags to indicate different levels. This makes things easier for now, and the levels can always be added later.
With the semester coming to a close, we've had to revise our goals somewhat. We hope to have a small sample set completed and imported into Archon (somehow), along with a front-end search interface for delivery. But it will likely be more bare-bones than originally planned, given the Archon issues we're having. However, there is talk of Joanna and possibly myself continuing work on the project this summer, so there will be more time to do some fine-tuning.
As I mentioned in a previous post, we ran into trouble importing our XML files into Archon -- basically, it seems it can't be done. We were hoping this would be easily fixed, but it has turned into a significant issue (or at least, a time-consuming one). John Osborn has been diligently trying to figure out a way to work around the problem, which so far involves converting the EAD into delimited files, importing those into Archon, then exporting them as EAD (I hope I've got that right -- it's a little confusing). It's a roundabout method to accomplish what should be a straightforward task, which Archon is supposed to be able to handle. There's obviously some glitch happening, but we don't know for sure what it is.
In searching online, I haven't found as much documentation as I'd hoped about how others have implemented Archon. I did read a blog post written by a librarian who had the same problem with importing XML files, although I haven't found any information indicating the cause or solution. The main task for the remainder of the semester may well be trying to figure this out.
We've been having meetings with Jen, John, Sue, Linda, and a new apps person, Raj, to discuss the import issue and the search interface design. The meetings are great experience because they give Joanna and I an inside view of how project management and workflow actually happen on the job. I feel less like a student worker than a professional and team member, which is a good feeling.
In addition, we've also been continuing to encode finding aids for the sample set using our template. After much debate about how to handle the intellectual hierarchy of the container lists, which can be hard to discern from the finding aids, we decided to simplify it as much as possible. This means not specifying levels like series, subseries or folder, and just using numbered container tags to indicate different levels. This makes things easier for now, and the levels can always be added later.
With the semester coming to a close, we've had to revise our goals somewhat. We hope to have a small sample set completed and imported into Archon (somehow), along with a front-end search interface for delivery. But it will likely be more bare-bones than originally planned, given the Archon issues we're having. However, there is talk of Joanna and possibly myself continuing work on the project this summer, so there will be more time to do some fine-tuning.
Monday, April 14, 2008
Week 9: Making a Template
The past couple of weeks, we've been having regular work sessions with Jen. We're each working on encoding separate finding aids, and then comparing our work to catch errors and inconsistencies and answer each other's questions. This is very helpful because when Joanna and I first started doing markup we felt kind of lost and didn't know if we were doing it right. Since Jen has more experience, having her do the coding along with us seems to be speeding up the learning process. I feel much more comfortable now, due to her help as well as the amount of practice I've had since the beginning of the semester.
Joanna and I also finally got a draft done of that template we've been planning for so long. I'm sure it will end up being revised, but it's nice to know we have some form of completed document. Our work in the coming week will likely focus on tweaking the template.
Since my last post, we also had a meeting with DLS folk to go over the search/browse interface for delivering the finding aids on Archon. Sue, Linda, and Bryan will be in charge of making our design a reality. The meeting was surprisingly short; I expected there would be the need for some negotiation of our design, but Sue and Linda didn't see any problem with implementing our original idea. It will be interesting to see what they come up with.
Speaking of Archon, we also tried to import one of our completed EAD XML files into the program. Unfortunately, Archon didn't like that and wouldn't take the file. This is problematic, as the whole point of creating a template is so the resulting customized files can be uploaded directly to Archon. Sue and John Osborn are working on resolving the issue, so we're keeping our fingers crossed. We have a meeting scheduled for next week with John to discuss the problem.
Joanna and I also finally got a draft done of that template we've been planning for so long. I'm sure it will end up being revised, but it's nice to know we have some form of completed document. Our work in the coming week will likely focus on tweaking the template.
Since my last post, we also had a meeting with DLS folk to go over the search/browse interface for delivering the finding aids on Archon. Sue, Linda, and Bryan will be in charge of making our design a reality. The meeting was surprisingly short; I expected there would be the need for some negotiation of our design, but Sue and Linda didn't see any problem with implementing our original idea. It will be interesting to see what they come up with.
Speaking of Archon, we also tried to import one of our completed EAD XML files into the program. Unfortunately, Archon didn't like that and wouldn't take the file. This is problematic, as the whole point of creating a template is so the resulting customized files can be uploaded directly to Archon. Sue and John Osborn are working on resolving the issue, so we're keeping our fingers crossed. We have a meeting scheduled for next week with John to discuss the problem.
Sunday, March 30, 2008
Week 7: Fun With Photoshop
Joanna and I got really burned out on encoding. I worked on my Louis Noun finding aid on and off for weeks, and am still only halfway through it because the container lists take FOREVER to mark up by hand. Therefore, we took a break from that last week to work on other neglected tasks.
Specifically, we're focusing on designing the interface that will allow users to search and browse the finding aids. This will include simple keyword and advanced searching, as well as browsing by topic, subject, creator, collection title, collection date, and form/genre. We came up with a list of topical categories for browsing, and worked on mapping EAD elements to MARC record codes for controlled access elements.
We also created a screen shot in Photoshop. It was fun to do something purely creative for a change, but we seemed to be barking up the wrong tree (we were sure Jen would be blown away by our idea to use expandable boxes rather than drop-down menus, but she politely nixed that), so we'll be going back and overhauling the whole thing. That's ok though, because it's an iterative process, as we learned in seminar last semester.
Our next goal is to complete a sample set of finding aids from the three collections (ignoring the container lists for now), and bring those along with our search page ideas to a meeting with Sue and Bryan at the end of the week. They will be responsible for the actual programming, so we'd like to give them something to work with ASAP.
Specifically, we're focusing on designing the interface that will allow users to search and browse the finding aids. This will include simple keyword and advanced searching, as well as browsing by topic, subject, creator, collection title, collection date, and form/genre. We came up with a list of topical categories for browsing, and worked on mapping EAD elements to MARC record codes for controlled access elements.
We also created a screen shot in Photoshop. It was fun to do something purely creative for a change, but we seemed to be barking up the wrong tree (we were sure Jen would be blown away by our idea to use expandable boxes rather than drop-down menus, but she politely nixed that), so we'll be going back and overhauling the whole thing. That's ok though, because it's an iterative process, as we learned in seminar last semester.
Our next goal is to complete a sample set of finding aids from the three collections (ignoring the container lists for now), and bring those along with our search page ideas to a meeting with Sue and Bryan at the end of the week. They will be responsible for the actual programming, so we'd like to give them something to work with ASAP.
Saturday, March 8, 2008
Week 6: Markup Madness
This post will be relatively short because I already wrote it once, after which it was immediately lost to the Internet ether when Blogger went down briefly (and didn't auto save my draft! Bad Blogger!). Here's a quick recap.
My main task this week was to continue encoding a sample finding aid in EAD using the oXygen text editor. Joanna and I each chose f.a.'s from the Iowa Women's Archive to mark up separately, after which we will compare notes and try to come up with an EAD template that can be used for all future finding aids. The next step after that will be to figure out how to plug the template into Archon.
The encoding has been a slow process, because we're using EAD samples we've found online to guide us and they're all a little different. Thus, there is a lot of revision and backtracking as we go. We've learned that EAD is pretty flexible and provides a lot of room for customization. At the same time, this can make it seem somewhat ambiguous and confusing. But I feel I'm making definite progress, and am learning a lot by getting my hands dirty with the actual encoding.
My main task this week was to continue encoding a sample finding aid in EAD using the oXygen text editor. Joanna and I each chose f.a.'s from the Iowa Women's Archive to mark up separately, after which we will compare notes and try to come up with an EAD template that can be used for all future finding aids. The next step after that will be to figure out how to plug the template into Archon.
The encoding has been a slow process, because we're using EAD samples we've found online to guide us and they're all a little different. Thus, there is a lot of revision and backtracking as we go. We've learned that EAD is pretty flexible and provides a lot of room for customization. At the same time, this can make it seem somewhat ambiguous and confusing. But I feel I'm making definite progress, and am learning a lot by getting my hands dirty with the actual encoding.
Saturday, March 1, 2008
Weeks 4 & 5: Field Trip
Oops. I forgot to post last week because all of us DLS fellows were immersed in the TEI at UIUC. The two-day workshop was intensive and kind of exhausting, but it was relevant to my project and helpful for understanding the text encoding process better. We learned how to use the Oxygen text editor, which will carry over to my work with EAD. And having experience with XML-based markup languages will be useful in general, so it was worth the trip.
To backtrack a bit, the week previous to the workshop Joanna and I had meetings with Wendy Robertson and John Osborn. Wendy discussed strategies for batch migration of legacy finding aids, and we spent most of the rest of the week playing around with that. The process we're testing involves creating tab-delimited text files of the finding aids, plugging them into an Excel spreadsheet, and figuring out how to make the various headings match up. This is easy if the finding aids have a consistent format, but not so easy otherwise. It's very time consuming to get the formatting right, so I'm not sure this method will work for all of the finding aids. We definitely have more work to do to figure it out.
We also talked with John Osborn from ITS about streamlining the process using some form of programming script. He's working on a template script for migrating the finding aids into Archon. Honestly, I'm not clear on this method yet, but hopefully will understand it better as we work on it more.
This week, Joanna and I continued working on the Excel spreadsheets and also practiced marking up finding aids in Oxygen. I'm not sure what else may be in store for next week, but will find out when we have a check-in meeting with Jen on Monday.
To backtrack a bit, the week previous to the workshop Joanna and I had meetings with Wendy Robertson and John Osborn. Wendy discussed strategies for batch migration of legacy finding aids, and we spent most of the rest of the week playing around with that. The process we're testing involves creating tab-delimited text files of the finding aids, plugging them into an Excel spreadsheet, and figuring out how to make the various headings match up. This is easy if the finding aids have a consistent format, but not so easy otherwise. It's very time consuming to get the formatting right, so I'm not sure this method will work for all of the finding aids. We definitely have more work to do to figure it out.
We also talked with John Osborn from ITS about streamlining the process using some form of programming script. He's working on a template script for migrating the finding aids into Archon. Honestly, I'm not clear on this method yet, but hopefully will understand it better as we work on it more.
This week, Joanna and I continued working on the Excel spreadsheets and also practiced marking up finding aids in Oxygen. I'm not sure what else may be in store for next week, but will find out when we have a check-in meeting with Jen on Monday.
Saturday, February 16, 2008
Week 3: Meetings
This week consisted of many meetings. On Monday, Joanna, Jen and I met with Sue Julich to learn about Archon, an open-source program for delivering finding aids online in EAD. Sue showed us the basics of the program, and Joanna and I later spent time exploring it ourselves. We plugged in some legacy (i.e. old) finding aids to see how it worked. The nice thing about the software is that you don't have to actually write any EAD code yourself, but can copy and paste text into boxes with the appropriate headers and an EAD document is automatically created. The downside to this might be a lack of control, and that's something we'll have to evaluate as we assess the program further.
We also had meetings with David McCartney from University Archives and Janet Weaver from the Iowa Women's Archives. Like our meeting with Greg Prickman, our purpose was to learn about the current state of finding aids and the typical workflow in those units. The upshot is that all of them have their finding aids available online as static HTML pages. The format and means of processing them differ somewhat from unit to unit, but there don't seem to be any major differences beyond that.
Finally, I spent more time researching EAD to get a firmer grasp on how it is structured and what the different tags mean. I still have a ways to go on that front, as the tag library is quite large. I also took notes from the book "Arranging and Describing Archives and Manuscripts" by Kathleen Roe, to get a clearer understanding of terminology used in the archives world (fonds, series, manuscript vs. record group, etc.) that may be useful for learning EAD.
Next week, there's a data migration meeting planned with Wendy Robertson on Monday. Aside from that I plan to continue doing research, working with Archon, and playing around with EAD tags. Over the weekend, I'll be attending a TEI (Text Encoding Initiative) workshop at the University of Illinois. TEI is a markup language similar to EAD. Hopefully, learning it will prove to be very helpful for this project.
We also had meetings with David McCartney from University Archives and Janet Weaver from the Iowa Women's Archives. Like our meeting with Greg Prickman, our purpose was to learn about the current state of finding aids and the typical workflow in those units. The upshot is that all of them have their finding aids available online as static HTML pages. The format and means of processing them differ somewhat from unit to unit, but there don't seem to be any major differences beyond that.
Finally, I spent more time researching EAD to get a firmer grasp on how it is structured and what the different tags mean. I still have a ways to go on that front, as the tag library is quite large. I also took notes from the book "Arranging and Describing Archives and Manuscripts" by Kathleen Roe, to get a clearer understanding of terminology used in the archives world (fonds, series, manuscript vs. record group, etc.) that may be useful for learning EAD.
Next week, there's a data migration meeting planned with Wendy Robertson on Monday. Aside from that I plan to continue doing research, working with Archon, and playing around with EAD tags. Over the weekend, I'll be attending a TEI (Text Encoding Initiative) workshop at the University of Illinois. TEI is a markup language similar to EAD. Hopefully, learning it will prove to be very helpful for this project.
Saturday, February 9, 2008
Week 2: The Fog is Lifting
While the first round of articles I read last week were definitely a bit over my head, I feel I am starting to understand better the whole concept of EAD and how it works. I generally need to try something out in order to really grasp it, so the time I spent yesterday actually working with an EAD document was pretty helpful. Jen had Joanna and I copy an EAD template online from a finding aid for a collection at the UC Irvine libraries, and replace the content with elements from Iowa Women's Archives finding aids. It was good practice, and helped me see how an EAD document is structured and how it relates to an HTML finding aid. I could only get so far with the document because the UC and UI finding aids were structured differently enough that they appeared to be only partially translatable. I also didn't understand what all the tags meant. There's still a steep learning curve to overcome, but it has gotten a little less intimidating.
On Thursday, Joanna, Jen and I had a meeting with Greg Prickman from Special Collections. The purpose was to assess the scope and format of finding aids currently being used in that department, to give us a clearer idea of what we'll be dealing with in planning the EAD migration. Joanna and I prepared a set of questions about the collections and how they are described. We learned that there are approximately 2,000 finding aids, and that they are all in HTML created from a standard template. This is good news, as it should make the creation of EAD records easier.
We will also schedule meetings with representatives from University Archives and the Iowa Women's Archive to learn about their collections. Next week, we will revisit the EAD templates we started; meet with Sue Julich to get an introduction to Archon, an archival information system; and continue doing research.
On Thursday, Joanna, Jen and I had a meeting with Greg Prickman from Special Collections. The purpose was to assess the scope and format of finding aids currently being used in that department, to give us a clearer idea of what we'll be dealing with in planning the EAD migration. Joanna and I prepared a set of questions about the collections and how they are described. We learned that there are approximately 2,000 finding aids, and that they are all in HTML created from a standard template. This is good news, as it should make the creation of EAD records easier.
We will also schedule meetings with representatives from University Archives and the Iowa Women's Archive to learn about their collections. Next week, we will revisit the EAD templates we started; meet with Sue Julich to get an introduction to Archon, an archival information system; and continue doing research.
Saturday, February 2, 2008
Week 1 (2.0): New Semester, New Project
After finishing up the recipe pamphlet digital collection over winter break, and taking a much-needed breather from school, I'm gearing up to start a brand new project this semester. And I have a partner! Joanna Lee and I are going to be working together on the Encoded Archival Description (EAD) pilot collection. I will again be working in Digital Library Services, with Jen Wolfe and Sue Julich as project mentors.
For any non-library types in the audience, EAD is an XML markup language that enables encoding of archival finding aids into records that are platform-independent, machine-readable, and fully searchable. In other words, it will allow users to search across various online indexes of archival collections, which are currently not standardized.
This project should prove to be fairly different from the previous one, as it will involve figuring out how to implement a new process that isn't yet in place. This will require researching how other institutions have used EAD and determining the best way to begin using it at the U of I Libraries. As I understand it, the end goal is to produce a prototype EAD collection on which to base future migration of HTML finding aids.
Our first assignment from Jen has been to research EAD and find case studies discussing its integration into other institutions' collections. We are looking at online resources and reading articles from LIS journals. On Monday, we'll be meeting with her to discuss what we've learned. The next step will be to start analyzing other EAD sites on the Web.
For any non-library types in the audience, EAD is an XML markup language that enables encoding of archival finding aids into records that are platform-independent, machine-readable, and fully searchable. In other words, it will allow users to search across various online indexes of archival collections, which are currently not standardized.
This project should prove to be fairly different from the previous one, as it will involve figuring out how to implement a new process that isn't yet in place. This will require researching how other institutions have used EAD and determining the best way to begin using it at the U of I Libraries. As I understand it, the end goal is to produce a prototype EAD collection on which to base future migration of HTML finding aids.
Our first assignment from Jen has been to research EAD and find case studies discussing its integration into other institutions' collections. We are looking at online resources and reading articles from LIS journals. On Monday, we'll be meeting with her to discuss what we've learned. The next step will be to start analyzing other EAD sites on the Web.
Subscribe to:
Posts (Atom)