Unit 13: Experiences, Challenges & Lessons Learned

This semester has been busy and at times frustrating.  I feel lucky in that I did not have any major problems with any of the installations.  In a couple situations I was able to go back to a snapshot in the VM and this solved the issue.  My main issue was my move in the middle of the semester and I was unable to connect the VM to the browser in the new place.  This put me behind in class but I’m glad I was able to eventually catch up.  While this class is challenging, it keeps my mind active which is I believe is important.  Over this semester we experimented with several repository systems such as Drupal, DSpace, EPrints and Omeka by entering our collections.  Each repository is unique and it is important to become aware of what they offer in order to determine which one best fits ones collection.  It is important to consider several factors when selecting a repository which include but are not limited to cost, long-term survival of files, metadata consistency, searchability/retrieval, physical appearance, ease of use, community and support, customization/flexibility, and ability to add plugins/modules.  Having exposure in working with the different repositories makes one realize the importance of such factors.  In addition, exposure in working with repositories ties in to the key concepts learned in the management portion of the class which includes the importance of proper storage, sharing and access of information.  Another key concept is the importance of librarians providing advice and support to researchers when managing their digital information. 

Unit 12: Omeka Continued

This week, we continued working with Omeka.  Plugins were added such as the OAI Harvester and Comments.  The idea of downloading a pre-installed VM versus building one’s own could be advantageous as it is will allow one more time to concentrate on the collection rather that spending that time on installing the VM.  Installing a VM is a time consuming process.  However, I did realize that after having installed a VM several times this semester the process became easier and took less time.  Installing a new VM each time also creates the problem for more errors as certain steps could be missed.  On the other hand, there are certain elements in the VM installation process that are beneficial to know such as the ability to: test for connectivity, check/change IP addresses if necessary, edit the host file.  By building a VM from scratch, the opportunity to learn about how a repository is structured and modified can be important if troubleshooting is required.  As my computer skills increase with the DigIn courses I appreciate more the behind the scenes components involved in building a repository from scratch.

Unit 11: Omeka

A new virtual machine and the Omeka demo were successfully installed.  Adding items to the collection was fairly easy and straightforward. The layout makes it easy to input all metadata required.   When logged in as a contributor, making an item public or featured is not possible whereas it is possible as administrator.  This makes sense as it allows users to contribute but needs approval from an administrator to make it public.  From a user and contributor perspective, Omeka is user friendly, easy to use and physically appealing.  The other home sites we worked with in class all seem to have its advantageous and disadvantageous.  The ability to add categories in Drupal provides flexibility; however, it can be time consuming at the forefront.  The ability to import Library of Congress Subject Headings and incorporate uncontrolled vocabulary in EPrints was a plus.  The process of cataloging the records in EPrints was straightforward; it was a matter of filling in the text boxes.  I recall that I did run into one problem for one of the records in which the creator was unknown.  Since creator is a required entry in which first and last name must be filled it, I believe I entered ‘unknown’ in both text boxes (first and last name).  For my collection, EPrints worked well; however, it lacked flexibility which could be a problem for other collections.

Unit 10: Open Archives Harvester

PKP Open Archives Harvester was successfully installed and my EPrints archive was harvested.  Additionally, I harvested records from three other repositories.  A federated collection is important to gather all pertinent information in one place.  When harvesting one has the option to harvest all sets or select from a list of sets which varies according to the archive.  As a result, it is important for a service provider to provide a list of sets to select from when harvesting in order to reduce harvest time and also to have the option to only harvest relevant information versus all of it.  The website http://www.openarchives.org/service/listproviders.html provides a list of registered service providers (although some links are broken).  The Networked Computer Science Technical Reference Library was partially working.  The site has a basic and advanced search, yet the screen looked the same for both.  Additionally, typing in the 'search for' text box would reveal no results. Scirus (for scientific information only) is well-organized and provides positive results when conducting a search.  ScientificCommons is cluttered on the homepage; it has a list of new publications and an advertisement.  I conducted a basic search and the results took too long to display, this was not the case with Scirus.  

Unit 9: EPrints Continued

I began to build my digital collection in EPrints.  The process of cataloging the records was straightforward.  The ability to import Library of Congress Subject Headings and incorporate uncontrolled vocabulary in EPrints was a plus.  Most of the records I entered consisted of articles and the categories available through EPrints were applicable.  Consistency when cataloging records can be an issue when different catalogers or even different repositories are given this task.  Everyone’s approach to cataloging may differ from others and it may even differ with the same cataloger.  Consistency may be obtained when working with a repository that has categories already listed versus inputting them.  The more I enter information in different repositories or content management systems, the more I realize there is something I should have added to another record.   Perhaps, experience could help with developing a consistent method in cataloging records.

Unit 8: EPrints

The installation and configuration of EPrints was successful.  A new Ubuntu server had to be installed on the virtual machine prior to the EPrints install which proved to be time consuming.  Web directory permissions were not configured during the server install (per directions).  However, when I had attempted to create phpinfo, I was unable to transfer the phpinfo.php document to the /var/www directory of the practice system using WinSCP.  Despite this, I continued with the EPrints installation process which went smoothly.  I stumbled a bit when trying to do the repository branding.  For some reason, I thought I had to edit the index.html but later realized I had to edit the index.xpage by doing the sudo nano command.

Unit 7: Digital Repositories

Workflow steps and more items were added to my collection in DSpace.  The ability to add, edit and approve items under the workflow steps allows for more control of the collection.  I also had the opportunity to experiment with DSpace as we will be moving on to Eprints in the next unit.  We look at digital repositories as a place for long-term preservation; however, Nancy John in her article Digital Repositories: Not Quite at Your Fingertips states “digital repositories will be for near-term access and not long-term survival” as a result of “the problems of permanent storage media and permanently usable file formats in permanently readable storage” (p. 192).  These problems are apparent and it is unclear if long-term preservation will be guaranteed.  Nonetheless, we can still strive for the goal of long-term preservation by improving current solutions (migration, normalization, emulation) and continue searching for more.

Unit 6: Installing DSpace and Adding to Collection

Moving along in class, DSpace 1.7.2 was successfully installed and configured.  In addition, I created a community, collection and added items to my collection in DSpace.  Overall the process went well, although I did have to return to a previous snapshot as one of the components (tomcat6) did not install properly the first time.  Thank goodness for snapshot.  In reviewing the DSpace installation instructions at https://wiki.duraspace.org/display/DSPACE/Installing+DSpace+1.7+on+Ubuntu, I would have to say a lot of the commands look the same as the instructions in the DSpace install provided by Professor Fulton.  Although they assume you already know how to install Ubuntu with no directions or links to directions.  In reviewing another set of instructions, http://wiki.lib.sun.ac.za/index.php/SUNScholar/Dspace, the images of the Ubuntu install are provided which are definitely helpful.  The Ubuntu and DSpace install instructions are thorough and I would be more inclined to perform the install with these instructions, although I may have some questions along the way.

Unit 5: Adding Tools to Drupal

This week we added some tools to Drupal such as the image module and CCK and Date fields.  These tools made my collection more presentable in addition to enhancing it.  For example, the fields are displayed in bold with the applicable information underneath it which made it more noticeable.  In addition, for the records consisting of an image, it was nice to see the image displayed in the record along with the other information about the image.  I ended up installing the lightbox2 module; however, I had wanted to add the audio module since I have one recording in my collection.  Unfortunately, in addition to having to install 3 other modules, the 6.x update is incomplete.  Overall, once the creator gets a handle of how to install and configure modules to enhance the collection, Drupal can be a suitable content management system.

Unit 4: Building Collection in Drupal

Entering my digital collection in Drupal has begun.  Drupal allows the creator of the opportunity to be as basic or extensive as one wants to be when developing the categories one wants to use for their digital collections.  Planning at the forefront and prior to entering any information is critical.  Already having a list of categories and controlled vocabularies makes the entering of information in Drupal a much faster and easier process.  In addition, I appreciate Drupal’s flexibility to allow categories to either be free-tagged or pre-defined.  When using controlled vocabulary, knowledge in this is greatly helpful.  The search function is definitely helpful for users; however it is critical that the record includes the necessary keywords that will allow users to find the information they are searching.  This is when tagging proves to be useful.

Unit 3: Pace of IRLS 675 Course

The tech assignments have moved along just fine.  Luckily, I have been able to install Ubuntu, VirtualBox and Drupal with minimal issues.  I look forward to working with Drupal and starting my digital collection.  Keeping up with the two discussions (technical and management) has been a struggle.  More specifically, keeping up with the readings required for the technical portion of the class has been a bit difficult.  Nonetheless, I do understand the importance of both discussion sections and appreciate how the management section has been included in the class.  Somehow, in the mist off all the assignments, I missed that we were supposed to post our digital object collection on the blog (which will be added to my Unit 1 post).  I did post my blog URL in D2l, but I have no idea how I missed the blog post. I plan to make a few changes to the titles of the blog posts I have previously posted for this course. 

Unit 2: Case Study Review on the Implementation of a Content Management System

In this course, we have been exposed to the advantages of implementing a content management system for the library web site. A study at Wheaton College was conducted explaining the experiences of the college using a content management system for the library web site. The case study is outlined in “Untangling a tangled web: a case study in choosing and implementing a CMS” authored by Terry L. Huttenlock, Jeff W. Beaird, and Ronald W. Fordham. The importance of the library web site at Wheaton College became evident when electronic resources boosted; however web site maintenance became a hardship. As a result, the library searched for an alternative: an open source CMS in which the web site could be maintained by non-programmers, have links to electronic resources, be straightforward, have the ability to migrate information from the old website, and be installed fairly quickly. Wheaton selected WebGUI. WebGUI provides support services (additional price), implements Perl, Apache and MySQL. Installing WebGUI required experience with mod_perl. The installation process was somewhat painless; however, at first navigating the system was a challenge as it involved a lot of figuring things out and knowing HTML. Once the system was figured out, it ran smoothly. Security issues were encountered after the first year; however, they were solved promptly. In the end, Wheaton was happy with WebGUI as updates and adding pages was simple. WebGUI was upgraded in 2004 which caused staff to learn how to navigate a new system and create a web site similar to the previous. Once again, the system was figured out and it ran smoothly. Wheaton was happy with WebGUI.

Reading this article was helpful as it makes one understand that there may be struggles when implementing an open source CMS; however, one should not be discouraged. It is important to think of the outcome and that in the end the new web site will be beneficial to its users.

Unit 1: Standard Install & Digital Collection

A new semester, a new course: IRLS 675.  After a year away from Ubuntu and VMWare I was a bit intimidated.  My VMWare had expired; therefore, I uninstalled it and downloaded a copy of VirtualBox for Windows.  I already had Ubuntu 10.04 LTS Server Edition – 32bit ISO downloaded and a MD5 checksum stated the hashes were the same.  I proceeded with the standard installing which included testing for outside connectivity by running a ping test, configuring aptitude, configuring a static IP address, providing name resolution via your HOSTS files, and configuring permissions on the Web site.  I did recall what rwx privileges meant. Lastly, I created phpinfo.  Overall, the process went smoothly and I did not run into any major problems, thank goodness.  I was stumped for a second when configuring the VM in VirtualBox.  I could not find the CD/DVD-ROM selection under Settings.  I had to go under the Storage selection.  I also remembered that I had to be careful not to make any typos.

Per an assignment, I gathered a small collection of digital objects focusing on Latinos in the information resources and library science profession.  The collection consists of digital images, sound files, and text files.  The digital images consist of pictures and the text files range from magazine articles, newspaper articles and dissertations written about and/or by Latino LIS professionals.  I was also able to find a recorded interview.  At the moment, the collection features six Latinos in the library field.  These individuals have worked in different LIS environments, on different projects and have positively impacted their communities.  Their contributions to the library field are highlighted in the collection.  Anyone interested in their contributions are most likely to access the collection.  Possible terms that may be used to provide access include: librarian, curator, digital divide, Chicanos, Latinos.  I would also use their names.  I look forward to entering this collection into Drupal.   .