Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

Visual Resources Project Workflow
(not Not a linear process; primarily LUNA):

Project Initiation:

? Establish project : o

  • team/leads

...

  • timelines

...

  • parameters

? Document User Requirements; should include the following: o

  • mock-up of end-user data window showing data element order and nesting,

...

  • list of thumbnail data fields and sorts,

...

  • list of standard searches,

...

  • describe controlled vocabularies,

...

  • describe standard abbreviations,

...

  • Determine if collection to be Inscribe enabled

...

  • if so, develop validations,

...

  • User agreement on stability of data structure and key values.

? Formalize Partnership o

  • Contract & Financial Arrangements

...

  • Setting of Expectations

...

  • Plan for Ongoing Maintenance

...

  • User Sign-off

Development:

Metadata

  • Determine Data Conformance

...

  • ---VRA compatibility, etc.
  • Finesse data as necessary (controlled vocab; clean fields, etc)

Luna Tech ?

  • Request Collection Set-up (usually Gale request this of Surinder)

...

  • Write Scripts/Clone Collection according to req. doc (Surinder)

...

  • Create Collection in Studio

...

  • ---create/modify catalogue template (G & M)

...

  • Load data (this can happen a number of ways

...

  • ---depending on format of data)

...

  • Set up Data Window Interface in Inscribe

...

  • Process Images and Upload into Collection

...

  • Once collection has been tested, move from "test" to "production"

...

  • Provide Support for Ongoing Maintenance

User Testing/Usability (write-up by Gale Halpern):

For a new collection:

Testing Procedure Description Staff
Functionality Simple searches by someone who is familiar with the database based on the search options (key word, date, etc.) and the data fields
Test the aspects of the collection that are unique - for example hierarchies.

User interface
Check the main elements of the home page (images, help page, contact information, background information, credits, etc.) to make sure that they are complete and easy to find

User help
There should be a help page with information on software, browser recommendations, contact information for help
Consistency Try out different browsers and versions (Netscape, Explorer)

Security
Test if the system is limited to a certain domain name or open access
Capacity
Coordinate 4-5 people searching the image database at the same time to assess impact
Performance
Connect to and search the system during different times of the day to test response time
Recovery
Backups, archiving load files
Maintenance
Error reporting, etc.
Documentation
Information about key aspects of the project (technical metadata)
Archiving
Safe storage of master images and source metadata, in addition to other contextual scripts and programs (METS, VRA model, etc.)

Usability 
Basic Checklist

For a Version Update or System Change:
? Test different derivative sizes
? Image Groups/Creating/Saving/Browsing and Client access under different logins
? Remote Launch Link
? Macintosh connections and use
? Links to web sites (webfeat, various URLS)
? Cross Collection searches
? Annotations

Promotion:

Strategies for Digital Collections Created by DCAPS (compiled by Fiona Patrick)
Focus on public access benefits and communicating value of the collections

I. Via CUL resources:

? Cataloging of collection as whole (Find Databases) and individual monograph/journal titles when appropriate - Networked Electronic Resource Form - http://www.library.cornell.edu/voyager/Order/netrescatform.htmlImage Removed
? Links and project summaries on http://dcaps.library.cornell.edu/facultygrants/Image Removed
? Announcement on CUL Gateway
? IRPC-L (which is in the process of being transferred to a PSEC list) or perhaps CU-Lib, so that we do not leave out anyone (selectors may be interested in new collections).
? InsideCUL article or announcement
? Announcements/articles in specific library print/online newsletters as related to collection. ex. Arts & Humanities news, Primary Source (Law Library)

II. Via CU resources:

? Press release and articles in Cornell Chronicle (FOCUS on CUL monthly column)
? Work with faculty members in announcing collections on their departmental websites
? Promoting it on Cornell website (www.cornell.edu)

III. Via global community:

A. Identifying Target Audiences
? Work with faculty members in announcing collections through their network of colleagues, listservs and conferences
? Work with library selectors
? Work with external organizations to publicize availability through their websites and publications (ex. National Trust for Historic Preservation (Tomlan) , Mountain Institute of Peru (Isbell), )

B. Mechanisms for wide accessibility
? Registering collections for Google results ranking - http://www.google.com/addurl/?continue=/addurlImage Removed
? Open WorldCat - http://www.oclc.org/worldcat/open/default.htmImage Removed cataloged CUL resources will be listed
? Announcements on broad digital collections and visual resources listservs (diglib@infoserv.inist.fr, VRA-L, IMAGELIB)
? Announcements/articles in digital library print/web publications (ex. D-Lib Magazine http://www.dlib.org/Image Removed )
? Future - CUL Digital Collections registry in development by Integrated Framework Team

Training & Support
? Improving Help & Contact pages
? Training Sessions for Faculty/ Users