Category: Project Updates (page 2 of 6)

JPEG2000 Support and Image improvements coming to the Digital Collections system

The Libraries’ Digital Collection platform (http://library.osu.edu/dc) is the home to many of the Libraries’ unique and distinct digital materials.  This includes access to materials of all digital content types, highlighting the broad depth of the Libraries primary resources.  And the system continues to grow, as the Libraries continues to work to move older, unprocessed digital artifacts into the Digital Collections platform, and will be a vital part of the infrastructure that enables the Libraries to continue developing robust, vital, long-lasting digital projects into the foreseeable future.

As part of the Libraries’ regular investments into its tools and services, a significant upgrade to the Digital Collections system provides access to digital images has been developed.  Starting so, the Libraries will be transitioning to using JPEG2000 to generate publicly accessible content, while continuing to utilize TIFF formatted images for preservation.  This format change and upgrade will not only improve the overall performance for the user, but will enable the Libraries to provide a better experience, with richer detail and functionality, without compromising our commitments to content rights holders whom request materials be made publicly available at a resolution, unsuitable for print publication.

But maybe you’re asking yourself, JPEG2000?  Print resolution?  I’ve heard of those things, but how does this really impact the user?  It’s a great question.  The simple answer, is that for the user, they’ll have access to better images.  Let’s look at a practical example.  This image demonstrates the representative experience that a user can expect when looking at a 35 MM slide in the current Digital Collections system: https://library.osu.edu/dc/concern/generic_works/2r36tz92c

If you followed the link, you likely had to wait for the image to show up (this takes about 2 seconds), and the resulting image is kind of blurry, and unable to be viewed at any higher resolution (i.e, you cannot zoom in).  Obviously, this isn’t an optimal experience for the user, but it’s been one that we’ve had to work with due to a variety of rights and policy issues.  But even within these limitations, we knew that we could do better.

By changing the underlying data format used by the Digital Collections system to JPEG2000, we can provide that experience.  Looking at this same image in the staging environment, we can see the difference right away. 

First, processing time to render the image is greatly improved.  On the staging system, rendering takes less than a second.  But more importantly, the initial image quality has improved.  Gone is the blurry image…by using JPEG2000, the Libraries can provide a crisp, clear user to the user.  And what’s more, the resolution can get better.  Using JPEG2000, we can provide up to 4 zoom settings.  So, for this image, the user can zoom in for better detail:

Zoom X 2

Zoom X 3

Zoom X 4

By implementing these changes, the Libraries will be able to provide the user a far superior experience, while at the same time, optimizing the content presented for the web. Each of the above images were generated from a 35 MM slide scanned at 2800 dpi, though the images provided through the browser are optimized for web viewing at 72×72 ppi (pixels per inch), rendering these images unsuitable for professional publication. 

This is really cool, how is JPEG2000 different?

JPEG2000 is a fundamentally different kind of image format.  Let’s consider the above images.  In the current Digital Collections system (pre-JPEG2000), zooming of images is done through the creation of lots of individual images at created at different sizes and resolutions.  So, for a typical image, this would mean creating a thumbnail, and then 4 image panels at the different “zoom” levels.  Since the system doesn’t know anything about the size of the image or the content, these zoom levels are generated through an evaluation of the source image’s DPI (dots per inch).  For most images in the Libraries, images are scanned for preservation at 600 to 800 dpi.  For a traditional 8×10 image, the process that we use to scale the images for “zooming” works pretty well.  However, for images of large size, or materials at higher resolutions (like 35 MM slides), the process results in poor quality access images.  Additionally, as you might guess, this process of creating lots of copies of smaller images requires a great deal of processing, which is why performance has sometimes been sluggish within the system.  Using JPEG2000, we are able to start looking at new ways to overcome these problems.  As an image format, JPEG2000 is a different kind of animal.  JPEG2000 was created as a wavelet technology, meaning that in addition to containing information about the original image, the JPEG2000 wrapper also contains technical metadata that defines how a JPEG2000 viewer can extract the various “zoom” levels from the image.

JPEG2000 Image Pyramid

http://www.astraguard.com/images/Pyramid.png

Unlike the current process, which requires multiple JPEG images to be created, a single JPEG2000 image contains all the information needed to generate different access representations.  Embedded in the JPEG2000 container is the original image with a set of mathematical data that generates a pyramid of accessible copies.  The benefit of this approach is that images generated through JPEG2000 retain the clarity and detail of the original source image, but are optimized through the decoder for low-resolution viewing.  JPEG2000 is heavily used within the cultural heritage community precisely because it enables this type of functionality.

If you are interested in learning more about JPEG2000, you can look at the following:

These are exciting changes, and will enable the Libraries to offer our users a digital object that more closely represents the physical slide (or photograph)…support our students, faculty, and world-wide user communities and continue to showcase the OSU Libraries as a world-class research institution.

 

–tr

AD&S 2017Q2 Report, 2017Q3 Plan

Website, Discovery, Collections

screen capture of an example special collections registry search

Special Collections Registry, focused on the Ohio Congressional archives

Much of the software and systems are now in place for the Website Redesign and we’ve started experimenting with navigation systems, revising the data models that we will use to build out the system, and have been integrating the work with the Discovery and Library Systems API, particularly in the Special Collections Collections registry. Each of these are in a beta mode, available to library staff and faculty and to some degree the public. Much of our work has been breaking out of the discrete boxes we had described them in and blended with our other projects so that they are behaving more like one large multi-faceted project.

screen capture of the unpublished discovery interface

Proof of concept of simultaneously searching across multiple indices.

 To this end we are going to be coordinating efforts on these projects between team members. In the coming third quarter, 2017Q3, we are looking to build out more of the website project, including Library locations and units, services and some initial static content, e.g. the About Us section. For the Discovery system we are going to be evaluating and improving the relevance the search results, and building a more advanced user interface for the search. For the Collections registry we will be adding a bit more information and then introducing to the general public. For all of these efforts we are asking for feedback and trying to identify and meet the expectations of online visitors.

Room Reservation

We have been working on two tracks for the Study Room Reservation System. We have been working towards improving performance on the existing system, as it is at points terribly slow. We have also been rewriting the system to use more modern programming and systems techniques — it is now several years old, so it is time. We want to have the new system ready for patrons by the end of the year.  That said, we’ll be rolling out more iPad display rooms in Thompson (like are currently in Research Commons) by the end of summer. 

Digital Collections & Exhibits

The Digital Collections system hasn’t had much of our attention this quarter, but we do have a few things planned for the next. We are investigating an upgrade to the latest software version and working on improving the image server and preparing to implement an Image Manifest endpoint. This will allow images to be easily re-used by researchers for things like collections combined across institutions and use of collection materials within our own exhibits program. We’ve been slowly migrating legacy digital projects to modern systems and exploring other tools that we might use to create new exhibits. 

 

 

Card Sorting In Action: UX Cohort Meeting

On Monday, May 15, Robyn Ness and Meris Mandernach lead another UX Cohort meeting for the Libraries Website Redesign project. This lively and informative session allowed the attendees to observe a card sorting exercise in action.

Nick Wilkenson and Judy Cerqua kindly volunteered to participate in the think-aloud exercise, together selecting what made the most organizational sense for content under a category. The goal was to reorganize content of the current Research Commons site. Some of the categories were: Home, About, Experts, Consultations, News, Rooms, and Events.

During the iterative redesign process, UX Cohorts can lead card sorting exercises with users, so it was helpful to see a live demonstration.

“This session was a great way for someone like me, who has never done UX testing, to see how it works in action and learn how to run a card sorting exercise. Robyn and Meris gave us great tips on how to get users to engage with the task.”

–Jennifer Vinopal, Associate Director for Information Technology

The group members were able to observe the process and ask clarifying questions.  From observing Nick and Judy doing the card sort, we learned how it’s helpful to pair people to talk through and try to come to an agreement for what goes where. Cohorts can ask participants about their thought process to encourage them to elaborate, but should be careful to not give the impression that their choices are ‘wrong’ in any way.

The pair didn’t agree on every decision, which often had to do with how one might interpret why a user is looking for particular content. In some cases, instead of assigning content to an existing category, they create a new category that they found to be more appropriate. At other times, they felt that content could be accessible from more than one category, to make sure it was as easy to find as possible.

Again, during this type of exercise, there are no wrong answers; the testers are instructed to group items in a way that makes sense to them. Robyn and Meris shared that in past exercises some people were able to complete the card sort fairly quickly, while others wanted to overhaul many of the categories, and still others were much more regimented in making sure all of the categories were assigned content. Another pattern that may emerge when there is quite a lot of content to categorize is that participants may re-assess their decision and move content after the first pass. Once they see the big picture, they get a better idea of how a user might search for information.

Meris and Robyn have even more interesting UX Cohort sessions planned. Would you like to learn more about this process and play a role in future user tests? Please join us at the next meeting to find out more.

Website Redesign UX Cohort Meetings: 3/15 and 3/27

Website Redesign UX Cohort Meetings, with project lead Robyn Ness and user experience lead Meris Mandernach

The first meeting of UX (User Experience) Cohorts for the Libraries’ user-centered website redesign project kicked off on Wednesday, March 15. Robyn Ness gave an overview of the role of a UX Cohort as part of the Libraries’ 2017 website redesign project. The group learned why usability is so important, and received an outline of general usability concepts. Robyn emphasized that, while we as library professionals are the functional experts for our services, we are not our users. As cohorts we will act as liaisons to investigating user needs.

Attendees then individually created personas that would be representative of someone using a service available on the libraries’ web sites.  Finally, everyone was asked to fill out a card to indicating what area they wished to participate as a cohort. A project of this size needs help with usability testing, data analysis, blogging, and more.   

The Thursday, March 27 meeting was led by Meris Mandernach and focused on those who indicated an interest in participating as a UX Cohort in some capacity. She provided an overview of the different types of user research, including but not limited to:

  • Card sorting. An investigatory style that will likely be used during our research. Subjects are given cards with subjects or other information on them and are then asked to group things that seem connected.  This helps develop the structure of the website. The challenge is that while it can be hard for those tested to think hypothetically, it does produce some interesting suggestions.
  • Contextual interviews. The library may conduct contextual interviews, as they allow both direct observation of and contact with the interviewee. The challenge of this type of usability research is that it can be time-consuming, and the intention is to move quickly on the redesign process.
  • Focus Groups. Gathering focus groups can be helpful, because it gives a bigger picture of what users wish to accomplish, and what is motivating them to use the website.

Other options are task analysis, first-click testing, heat maps and user surveys. All can provide a wealth of information to analyze how our site is used. Multiple methods will be combined as needed. 

Meris answered some follow-up questions from the attendees, clarifying how usability testing can help guide the redesign process. Finally, the cohorts broke into groups based on project assignments and discussed their roles. 

Cohorts are encouraged to check for updates at the Website Redesign Project Wiki, and if they have further questions, reach out to Meris Mandernach (mandernach.1) or Robyn Ness (ness.16).

The next meeting (being scheduled soon!) will delve further into card sorting, followed by more group project time.

IT Projects for January-March 2017

  • Digital Collections | Finding Aids Integration
    Implement a prototype for viewing Digital Collections information in Finding Aids generated from Archivists’ Toolkit, and vice-versa
  • Digital Collections | Image Server Upgrade
    Implement Kakadu image server to increase efficiency in image delivery
  • Archivists Toolkit | Finding Aids Publishing
    Automate some aspects of SCDA’s process in publishing Finding Aids from Archivists’ Toolkit to increase staff efficiencies
  • Digital Initiatives | API
    Develop an API to facilitate the interoperability of various Digital Initiatives projects and provide programmatic access to library resources
  • Discovery | Search Results Proof of Concept
    Experiment with consuming a few data sources via their APIs and and test usability of search results presentation (per Discovery Inquiry report)
  • Room Reservation System | Responsive Calendar
    Implement a more responsive and intuitive calendar for navigating room schedules
  • Room Reservation System | On Demand Reservation at Research Commons
    Reserve a room on the device as you are standing at the room
  • Suma Enhancements | Research Commons
    Enhance and contribute back to NCSU’s Suma physical space usage assessment app
  • Platform as a Service | Research Commons
    Develop interface for Research Commons to on-demand provision temporary sandboxes for researchers on platforms such as Omeka, Scalar
  • Website Redesign
    Continue efforts to build out new CMS and to analyze content
  • Update Sierra database and Dspace
    working with AD&S and external vendors
  • Pc refresh for all of Thompson staff machines. 
  • DUO multi-factor authentication
  • Bring in hardware solution for VPN
  • Doing backups directly to OCIO from SOCC
  • Replace iSCSI switches at SOCC
  • Work to refresh SOCC and Dreese data centers storage and NAS controllers
  • Install and deploy JAMF Pro software to manage Macs and iPads

  • Clean up Active Directory groups and users

  • Create new Active Directory

  • Work implementing all CIS/OSU benchmarks for servers, switches and firewalls
  • Begin work with OCIO on replacement for mobile device management
  • People counter

Project Updates 2016Q4

October 2016 – December 2016

This is based on work completed December 6, 2016

Digital Collections

  • (tick) Post-Sufia 7/Fedora 4.5 Clean Up
    Data migration and functionality clean-up crept well through October and even into November. The system soft launched on November 8, and then fully cut over on November 16, 2016.  We have been making some small changes to the way things are indexed, displayed, organized, but overall we have finished the migration.
  • (tick) Non-Image Items
    We have tested and adjusted the display of non-image content in Digital Collections, including pdf, Word docs, and progressive streaming for audio and visual derivatives.
  • (warning) (blue star) OAI Export Server
    Ohio is now a part of the DPLA. This means that we’ll need to look at implementing an OAI output/server as part of Digital Collections by the first of the year.   We are looking at implementing a plugin yet this year.
  • (minus) Controlled Vocabulary
    Allow data entry to select and record controlled vocabulary entries for certain Digital Collections fields. We are unlikely to make much progress yet this year, reflecting both the state of the community and our workload.

Non-Digital Initiatives

  •  (tick) Room Reservations Updates
    There are several outstanding enhancement requests for the Room Reservation System. New responsive calendar plugin and editable reservation title are expected to be completed by end of 2016.
  •  (tick) SUMA Space Use Assessment (for Research Commons)
    App should be installed and tested by end of 2016.
  • (minus) Discovery Inquiry/Pilot (on hold)
    Work with SDIWG/DSMWG to develop and user-test a proof of concept presentation of different data sources (via APIs) into a unified library search with a modular result display, grouped by commonality.
  •  (minus) Hours/Locations (*subsumed by website redesign project)
    There have been requests for fixes and enhancements of the Hours/Locations app/widgets. We also have collected useful feedback from the locations focus groups. And we would want to add additional data elements to the app so the information can be leveraged by other apps and future website via API. 

Internal

  • (warning) Migration Off of OCIO Web Hosting
    Work to get the remaining content off of the OCIO Web Hosting server.  They are changing the terms of their hosting service, and we are coming to rely less and less on this platform. Remaining features that need to be migrated are documents, downloads, projects (exhibits and albums), staff, and wikis. Should be completed early 2017.
  •  (warning) Drupal Infrastructure
    Stand up multi-environment Drupal infrastructure, build test modules for pulling in data from APIs, and plan project.
  • (tick) IT Help on Confluence
    Launched a self serve documentation center at go.osu.edu/libithelp. Will have all IT CarmenWiki content moved to local Confluence by end of year.
  • DSpace Upgrade 1.8 to 5.6

Key

(tick) – likely to be completed this quarter
(warning) – possible completion this quarter
(minus) – not likely to be completed this quarter
(blue star) – project added after beginning of quarter

Finding Aids Publishing

Screen capture of a typical sample of a finding aid.The IT Division has been collaborating with the Special Collections Description & Access (SCDA) team to implement an Archival Description Management System (ADMS). The software, Archivists’ Toolkit (AT), is the focal point of an effort to provide a central point for the records about the materials housed in our Special Collections.  AT is very effective at allowing staff to record accessions, organize records, and search for materials. We still need to get this information into the hands of researchers; this is why we are publishing Finding Aids for each collection.

Screen capture of Search This Site buttonAT is able to export the data in a standard format, Encoded Archival Description (EAD). This xml format may sound familiar, as it is what we have been using in the OhioLINK Finding Aid Repository.  This document encapsulates a great deal of valuable information about the collection and what it contains.  We were able to slightly modify the style sheets that came with AT to allow web browsers to transform the native XML into nicely formatted HTML.  The SCDA team publishes the EAD files to our web server and the search engines are able to pick it up.

Screen Capture of a Google Custom Search

AD&S is working with curators to provide links to these finding aids from their collection web pages, but we are also able to search them via the Search This Site feature on the OSUL website.  After you enter your search term, you can limit it to just finding aids,  using the tab.

 

So far we have finding aids up for a few collections, but we have lots more in the works, please check them out!

 

IT Project Prioritization for 2016Q1

Prioritized for 2016Q1 (January 2016 – March 2016)

Pending

  • Reading Room workflow & patron data collection streamlining (meeting to discuss scope on 12/8)
  • Upgrade Atlassian software to include Service Desk and Knowledge Base/Confluence modules (subject to testing and purchase approval)

Discovery

  • Non-Image Files in Fedora – Information Gathering about requirements to include other digital assets.
  • Search & Facet Interface for Finding Aids – Information Gathering for search apparatus for Finding Aids, possibly as a pilot for searching all Digital Initiative assets.
  • Possible consolidation of physical location information on websites – focus groups
  • Exhibits, galleries and albums on OCIO web hosting (per charge of Web Governance Committee)

Implementation

  • Large File/File Set Uploads in IMS – Implement the ability to upload large sets of images via non-web interfaces, e.g. Shared Drive/FTP. Currently the maximum size is ~500mb.
  • Image Server Improvements – Upgrade image server internals (e.g. from RIIIF to Lorus)
  • IMS Improvements – Product Owner choice of most valuable changes to implement in a set amount of time, likely controlled vocabularies
  • Exporting & Publishing Finding Aids from Archivist Toolkit – to make accessible to patrons

Continue reading

Mid-Quarter Project Report 2015Q4

Report as of November 23, 2015. Please contact Russell Schelby if you have any questions or concerns.

Information Gathering

(tick)AS-166 Publishing and Managing Finding Aids

Based on information gathering sessions with curators and cataloging staff, requirements and a simple phased plan for publishing finding aids from Archivist Toolkit has been developed. It is recommended that the first phase of this plan be implemented in the next quarter.

(plus)IMS-504 Image Collections Complex Objects

One of the next steps for our Image Collections system is to be able to use complex objects, that is multiple images around the same described object, e.g. the front and back pictures of a manuscript leaf. This quarter’s task is to gather information on what requirements this enhancement would need; these sessions are just in the planning phases, but should be easily completed by the end of the quarter.

(warning)Co-Curricular Tutorials

We identified several potential candidate WordPress plugins. Partner has not had time to test.

Development & Implementation

Digital Initiatives

(plus)AS-48 Archival Description Management System (ADMS) Data Migration Assistance

This project encompasses all of the data that needs to be migrated into ADMS from various sources, including ArchivesSpace, OhioLINK EAD Repository, vendor provided EAD, Sierra data, certain Past Perfect data and other various bespoke data sets. So far, Darnelle Melvin has been working on the transformations for importing ArchivesSpace data into ADMS. AD&S has only been minimally involved. As expected, the migrations will not likely be complete this quarter.

Continue reading

Mid-Quarter Project Report 2015Q2

The following projects were approved for Quarter 2, 2015, April 1 to June 30.  The projects were arranged into three tiers of priority to help guide our work. This report describes progress through the 9th week of the quarter.

Tier I (Highest Priority)

  • ArchivesSpace Production Support (Product Owner: Cate Putirskis)
    The project team collaborated with Lyrasis to isolate the re-ordering issue and develop a patch for resolving it.  This fix has been tested in a development release, but has not been released for a production instance yet. We expect to have the release available in mid-June and will plan testing and upgrading the software.  The SCDA and Special Collections groups have been continuing to use the software for creating Accession records as well as uploading Resource record sets with the knowledge that data order will need to be redressed once the patch is in place. AD&S has developed a prototype for reordering Resource elements based on title, but will need to extend that to order by container data. Looking forward, the team participated in the selection process for next development efforts to be undertaken by the Lyrasis development team, especally anticipating the Location Management changes effected by “that Yale plugin”.
  • ArchivesSpace Data Migration – Import existing Special Collections data into ArchivesSpace (Product Owner: Cate Putirskis)
    This next phase has not been fully engaged, only beginning to identify the data from Sierra and conceptualizing the data we’ll need to import.  This project has unfortunately been delayed by resources committed to resolving the production issues around our ArchivesSpace installation.
  • Image Management System Import Cartoons and Byrd Polar Media Manager collections and deliver a production public interface (Product Owner: Morag Boyd)
    This project is reaching the final stages for this phase. Development around the Public and Back-End user interfaces is complete. Staging and development environments are being implemented and tested. Decisions on the metadata structure are being finalized and implemented and we are working through the importing scripts.  We are slightly behind where we wanted to be, but believe that we’ll be ready to move into production on schedule.
  • DSpace Upgrade to 5.x Practice upgrade with Longsight (Product Owner: Maureen Walsh)
    The team worked with our vendor to successfully complete and document a practice upgrade of a copy of our production code base and assets to DSpace 5.2.  DCS is in the process of reviewing this system to identify needed configuration changes and to itemize a list of customizations (code modifications) that would be required during the “real” upgrade. AD&S feels confident that our developers can perform future upgrades.
  • Identifier Resolution Service Review use cases and design solution (Product Owner: Terry Reese)
    Initial requirements and possible technical solutions have been had initial exploration. Further examination of needs against possible solutions will be the next step and an implementation plan developed.

Tier II

  • Room Reservation Enhancements – Improve system based on user feedback (Product Owner: Lila Andersen)
    We have started on the requested enhancements, with the first round of modifications fully tested and ready for production.
  • Co-Curricular Tutorial Delivery – Develop plan for migration of Net.Tutor to new tutorial platform/system (Product Owner: Karen Diaz)
    An instance of Moodle is ready for testing by Teaching & Learning. If Moodle does not meet the needs of T&L, we will continue our research into possible solutions.
  • Explore Video/Audio Preservation/Management System – Develop requirements, stand up Avalon (or equivalent) for exploration
    No progress.
  • ILLiad Interface Enhancements Improve usability and mobile responsiveness of Illiad (Product Owner: Brian Miller)
    User interface mockups have been developed with the Product Owner. Implementation can begin with the onboarding of a front-end web developer.

Tier III

  • Digital Exhibits Platform – Research and evaluate Spotlight
    The Digital Exhibits Working Group and the Head of Digital Initiatives are recommending adoption of Omeka as a platform for digital exhibits. (Digital Exhibits paper is due June 8) IT proposes that we consider developing a method for linking Omeka items in digital exhibits to objects in the Master Objects Repository, as there has been no progress in the community on an Omeka 2.x to Fedora 4 connector.
  • BuckeyeSensor Interface – Design and implement prototype interfaces
    No progress.
  • Special Collection Reading Room Patron Management – Develop requirements (Product Owner: Lisa Carter)
    The team has been conducting interviews with reading room managers. Documentation of current workflows, similarities and differences between processes, and pain points is in progress. We have recommended a couple short-term steps to increase efficiencies.

Other Work

  • Carmen Library Link/LibGuides Implementation
    This project wasn’t prioritized, as we didn’t have much work left to do on it. The team is obtaining the final data streams and setting it up for testing and training with the LibGuides implementation team in the next few weeks.
Older posts Newer posts