Islandora vs. SobekCM Update ( March 2013 )

MISSING IMAGE

Material Information

Title:
Islandora vs. SobekCM Update ( March 2013 )
Physical Description:
Report
Language:
English
Creator:
Digital Initiatives and Services Committee ( DISC )
Digital Initiatives Subcommittee ( DISC )
Publisher:
Digital Initiatives and Services Committee ( DISC )
Place of Publication:
FL
Publication Date:

Subjects

Subjects / Keywords:
Competencies

Notes

Abstract:
The Islandora column of this evaluation was updated by FLVC and represents our current understanding of the capabilities of the Islandora version 7 system which, as of February 25, 2013, has not been released into production. Exact answers regarding the capabilities of the Islandora system (e.g, the new Books, Bookmarks, OAI, OCR, Paged Content, Newspaper and Video modules) cannot be provided until the production release of version 7 has been installed an evaluated. Changes to the current Islandora evaluation in some cases vary significantly from the prior evaluation due to the modification to the definition of the "o" character, which now requires a confirmed date.

Record Information

Source Institution:
University of Florida
Holding Location:
University of Florida
Rights Management:
All rights reserved by the source institution.
System ID:
AA00007675:00002


This item is only available as the following downloads:


Full Text

PAGE 1

x = does not currently meet requirement A Architecture Islandora Comparison SobekCM A1 Architecture supports multi-site use. A2 A2a Architecture allows multiple levels of user permissions, which can be configured based on collections, collection groups, or institutional units, for example. A2b Various levels of administrator and staff user permissions are available for institution staff to change system settings and content. A2c Simple and secure user (non-administrator) account creation is available for students and faculty to upload files and add metadata. A3 Architecture facilitates library staff in setting up collections and assigning or ingesting items to collections. A4 System does not require users to have a static IP address. A5 There are no conventions that must be followed for naming directories or files, or the conventions are documented, verified, and easy for library staff to follow or create, and/or they are followed through an automated process as part of a tool or application. A6 Collections are logically, not physically, defined; they are easily created, deleted and redefined by library staff. A bibliographic item can easily be added to a collection, assigned to a new collection, allocated to multiple collections, or removed from a collection by library staff. A7 page within the platform from an outside discovery tool, the path back to that tool should be clear and automatic. x x A8 Text can be stored in appropriate flavor of Unicode as necessary A9 Evaluation of Islandora & SobekCM The systems were originally rated against each of the requirements from the list as follows below. Enhancements not covered by this initial process are covered in additional sheets. User permissions: Indexes: FLVC Update 2/25/2013: The Islandora column of this evaluation was updated by FLVC and represents our current understanding of the capabilities of the Islandora version 7 system which, as of February 25, 2013, has not been released into production. Exact answers regarding the capabilities of the Islandora system (e.g, the new Books, Bookmarks, OAI, OCR, Paged Content, Newspaper and Video modules) cannot be provided until the production release of version 7 has been installed an evaluated. Changes to the current Islandora evaluation in some cases vary significantly from the prior evaluation due to the modification to the definition of the "o" character, which now requires a confirmed date.

PAGE 2

A Architecture Islandora Comparison SobekCM A9a Indexes can be updated to include new or changed content without having to reindex the entire database A9b Indexing runs in the background (no downtime for using the system during indexing). A9c New items can be indexed in real time so that they are available to the public immediately. A10 Collections can be created, populated, and viewed by authorized users while remaining invisible to unauthorized users. A11 Customizations can be tested by library staff in a way that is invisible to unauthorized users and that does not affect the rest of the system. Having a test function within the system would satisfy this requirement, as would having a separate test instance of the system. A Architecture Islandora Comparison SobekCM A12 All content from the current PALMM Collections can be imported into the system with no loss of information or functionality. All content in UFDC Sobek, USF Fedora, UCF CONTENTdm, non-PALMM DigiTool, and other current SUS systems can be imported into the system with no loss of information. x A13 A13a (a) The system components are affordable, dependable, and supportable by existing staff resources. This includes all software required to run the digital library system in actual operation: database, operating system, digital library software, and support software required in addition to the digital library software itself. A13b (b) Open-source tools will be weighted more heavily because they can be tested, validated, maintained, developed, and budgeted to a more exacting level for more accurate initial requirements and future projections. A14 System natively supports content in multiple languages. A15 The system supports multilingual interfaces For example, automatic support if library staff provides translations; or set search terms already automatically supported with translations already in place. A16 Documentation that is usable accompanies the code including clear and concise comments and examples. x A17 Custom configuration settings are available at the collection level for collection-specific behavior and appearance with collection settings overriding global settings. x A18 Custom pages allow the creation of collection home pages and other landing pages based on institution, format, topic, etc. x B Content Islandora Comparison SobekCM B1 file relationships and structure, including multimedia collections. x B2 B2a TIFF images B2b JPG / JPEG images B2c JP2 / JPEG 2000 images B2d Single-page and multi-page PDFs B2e Text System support: The system must support at least the following formats:

PAGE 3

B Content Islandora Comparison SobekCM B2f Audio B2g Video B2h Streaming audio / video (URLs to streaming server) B2i Remote content (URL links to externally stored files and embedded viewers as applicable) B2j Files intended for download rather than display (e.g. data formats, spreadsheets) B3 B3a EAD finding aids (with structured display, links to digitized content, XML to HTML translation and option to also display as PDF) x B Content Islandora Comparison SobekCM B3b Serial display with hierarchy (for newspapers, journals, and other serials) x B3c Audio for simple object (music file alone), and for complex/compound objects (oral history with a transcript that can be displayed while audio is played) B3d Books/monographs (structured table of contents, page turning and "go to") x B3e Newspapers (NDNP and METS/ALTO formats, search term and full article segmentation highlighting) x x B3f TEI-encoded full-text x B4 B5 Must support related objects, defined as groups of objects with some relation to each other, such that: if one is retrieved, all are retrieved the relationship among the objects is made clear related objects do not have to all be in the same format any number of related objects can comprise a group B6 Must support complex objects with METS structural metadata. Must preserve METS for export. x C Metadata Islandora Comparison SobekCM C1 System has documented, verifiable support for ingest, display, and translation of the primary descriptive metadata in use work for museums, archives and gallery collections as well. C2 C2a Input/update metadata C2b Add local fields (including administrative fields not shown to the public) C2c Ingest existing metadata records C2d Edit ingested existing metadata records C2e Export metadata records C3 Metadata can be created/edited online, or created offline and uploaded C4 The system supports the following special genres: DL System has a readily available easy process and tools for library staff to: Metadata can be:

PAGE 4

C Metadata Islandora Comparison SobekCM C4a In the system before an object is in the system and associated with the object when the object is loaded C4b Added to the system at the same time as the associated object is loaded C4c Added to the system and associated with an object after the associated object is loaded C5 C5a Simple Dublin Core C5b Qualified Dublin Core C5c MARCXML x C5d MODS C5e VRA Core C Metadata Islandora Comparison SobekCM C6 Pre-existing metadata in the above formats can be loaded as XML records or as tab-delimited or CSV files with associated mappings. x C7 It is possible for library staff to design our own metadata input/update templates. C8 Simple forms for metadata entry can be provided for untrained users (for IR functionality). C9 It is possible to include technical and administrative metadata elements which do not display to the public. C10 It is possible to enable and maintain a controlled vocabulary (standardized or user generated) for any given field. A tool or method is available for making desired changes easily in a manner that meets library staff needs. x C11 Bibliographic records from the Aleph library catalog, OCLC records, or any MARC records from anywhere, can be easily imported into the DL system. C12 The system can expose metadata to search engine crawling/indexing to ensure good coverage in major search engines. x C13 EXIF and IPTC metadata embedded in JPEG and TIFF images can be automatically extracted. Users may map this metadata to Dublin Core or Qualified Dublin Core fields. x D Ingest Islandora Comparison SobekCM D1 Metadata can be harvested from OAI-PMH accessible collections for inclusion in the DL. D2 D2a Manual upload to ingest D2b Automatic batch upload to ingest x D3 If any translation/conversion is needed prior to ingest, a documented process with a tool/application is available that library staff feel is sufficiently simple and has adequate support for their needs. D4 Provides immediate verification of ingest success or, in the case of ingest failure, provides error messages that communicate to staff what needs to be fixed for successful ingest. D5 Ingest processing is speedy enough to meet library staff needs. (For each DL System under review, discussions over the value of increased speed should consider the benefits of that speed in relation to the costs/delays for staffing, software version upgrades, etc). Has input forms and edit routines for descriptive metadata in: The system supports both:

PAGE 5

D Ingest Islandora Comparison SobekCM D6 Thumbnail images can be created at the time of ingest from all image and document formats supported in the system. Default resolution and size can be over-ridden at ingest. D7 Custom thumbnail images created outside of the DL can be: D7a Added to the system at the same time as the associated object is loaded x D7b Added to the system and associated with an object after the associated object is loaded. D8 The system can automatically create multiple file formats from TIFF images. The process should be testable so that library staff can evaluate the process of creating derivatives and products (multiple manifestations created from the TIFF file) for quality and any other needs. File formats available for automatic creation from TIFF include at minimum: D8a Searchable full text via OCR D Ingest Islandora Comparison SobekCM D8b JPEG2000 images, with library-defined resolutions (not just a default set that cannot be changed) D9 D9a Create derivatives and do not store TIFF D9b Store TIFF but do not display to users D9c Store and display TIFF to users. D10 The system can automatically index full text from formats including PDF, Word, Open Office, HTML, and XML. D11 When a complex object with manifestations exists in the system, it should be possible to replace a specific file or files without having to reingest the entire object. D12 The system can accommodate a single ingest process for universities using ProQuest ETD Administrator (Possible SWORDlike process?) D13 D13a Non-staff, authorized users can submit content and metadata by a simple process D13b Content and metadata are not added to the system (or are added with provisional or non-display status) until reviewed D13c Authorized staff are enabled to review and approve, edit or reject metadata and content D13d Submitters are notified by email, text message, or other electronic communication about the approval status of the item. x E Search and retrieval Islandora Comparison SobekCM E1 System has a Z39.50 server, equivalent JSON interface, or other documented system-access method. E2 Users have the option to search or to browse. A simple search view (single search) is always available. E3 For serial publications, the user should be able to search for individual articles by author and title. The user should also be able to list and browse the tables of contents of issues, listed in reverse chronological order. E4 The user can choose to search metadata only and both metadata and full text together. E5 Both Google-like simple search (all fields, one search box, all terms OCRed) and advanced search (choice of specific fields, limits, choice of Boolean operators) are allowed. System offers an IR mode of ingest, that supports the following functions: The system should provide options for how uploaded TIFFs are handled, for example:

PAGE 6

E Search and retrieval Islandora Comparison SobekCM E6 E6a Within a single collection E6b Across all collections E6c Across groups of collections defined by staff E6d Across ad hoc groups of collections defined by the user E7 Assistance for search and navigation is provided through: E7a Alternate suggestions when no results found x E7b Faceted browsing E7c Clickable links within metadata (author, subject, format, etc) E7d Pre-determined canned searches E Search and retrieval Islandora Comparison SobekCM E8 Hits are displayed in a way that makes sense to the user; it is clear whether an object is a book, photo, recording, etc. x E9 E9a Any of these can be set as the default view by the user for that session / account E9b Any of these can be set as the default view by staff for general use E9c Different default views can be set for different collections E10 The results returned from a search can be represented visually in document space ala AquaBrowser or similar tools. x E11 When performing a cross-collection search and retrieving hits from multiple collections, it is clear to the user which collection each hit comes from. E12 F Display and Use Islandora Comparison SobekCM F1 An outline or table of contents display is available for complex structured bibliographic items. It is possible to expand and contract any heading in the outline hierarchy. x F2 F2a The number of occurrences of the term in the object is displayed in the list of hits. x x F2b When the textual object retrieved by a full text search is displayed, the search term is highlighted on the page. x x F3 When multiple manifestations (e.g. image and full text, audio and transcript) are available, they can be displayed simultaneously on the screen. F4 Branding is obvious, explicit, and restrained as wanted for both collection owning repository (could be library, museum or agency) and the digitizing repository (could be library, museum or agency). The branding is in place at the collection level and item level (all views). F5 Multiple brands (icons) can be associated with and displayed with an object. Users can search and browse: The results returned from a search should be sortable by author, title, publication date and relevance: When a textual object is retrieved by a full text search:

PAGE 7

F Display and Use Islandora Comparison SobekCM F6 All collection items display under a collection specific to the collection-owning repository, as well as in other collections as selected by the collection-owning repository. F7 Users can display, download, print and/or email content (unless these functions are restricted for a particular computer file, bibliographic item, or collection). x F8 Restrictions on access and use can be implemented at the computer file and/or the bibliographic item level by password and by IP filter. When an object is restricted, the restriction is clear to the user. F9 Objects and records may be restricted under embargo, ideally with automatic release of the embargo once it expires. F10 There is a portfolio ("my collection") function for end users. x F11 The implementation can control display characteristics such as what fields and labels are used. F Display and Use Islandora Comparison SobekCM F12 The end user can control some display characteristics such as the number of hits to show on a page and how the results are displayed with options such as thumbnail, citation only, title only, and hierarchical (for newspapers and volume/issue materials). x F13 Easy to understand help files and/or tutorials are available to assist users with search, display, and use functions. x F14 Interface should be attractive and easy to use. F15 the user community has effective input into the design/development process. F16 x F17 Links (URLs) embedded in any field will display as clickable links. The system has a convention for representing anchor text to display as an actionable link instead of the URL. F18 F19 Share feature: Users can share an item via email, Facebook, Twitter, or other social networking sites. x F20 item can be displayed. x F21 F22 User can save searches x F23 User can see search history. x

PAGE 8

G Export Islandora Comparison SobekCM G1 The system can export simple objects as files and associated metadata. G2 The system can export both simple and complex objects as packages with METS descriptors. x G3 Regardless of the format of origin, bibliographic data can be exported in MARCXML for import into a catalog system. G4 There is an OAI broker capable of exporting all metadata, regardless of the format of origin in oai_dc format. G4a Custom OAI sets can be created using a logical search of content. G4b OAI harvesting can be disabled for certain content (test content, incomplete collections, etc) G5 Designated content can be exported from DL to FDA automatically, without additional effort (sending, processing, any manual work) on behalf of library staff. x G6 User can export a set of saved items (portfolio) for use by another tool (e.g. Omeka). x H Management and reporting Islandora Comparison SobekCM H1 Ad hoc and canned reports can be run. Documentation is available on existing automatic reports and samples of reports are available for evaluation by library staff for their needs. H2 H2a Number of searches (by collection, by object contributor, and by date/time) x H2b Materials accessed (by title and aggregated into various categories) x H2c Users x H2d User sessions x H3 Sample usage reports are available for review by library staff H4 H4a By collection H4b By contributor H4c Created since [date] H5 H5a By collection H5b By contributor H5c System wide H5d Title and single volumes for serial items so that the usage is tabulated for both single issues and for the aggregate of all volumes for the particular serial title H6 The system keeps a count of the number of times each bibliographic items is rendered, and can display this with the metadata for the item in the public interface. x H7 The system can automatically send monthly reports to authors regarding their usage statistics. x The system can provide a report of the most popular titles in a specified time period The system automatically logs usage statistics which can be aggregated for any time period on: The system provides counts of objects at both the bibliographic and file level:

PAGE 9

I Budget Islandora Comparison SobekCM I1 The DL System has clear cost figures for the existing system and enhancements. x I2 When evaluating the DL System, cost considerations should include: licensing cost cost per record costs of additional software for the DL System host costs of additional software/tools for each of the libraries review that detail implementation plans) x