AuroraDL Committee

From Digital Libraries - Fall 2008

Jump to: navigation, search

Contents

[edit] Committee Members

Andrew Clark, Bharti Joshi, Jasur Yahshiyev

Contact/point person: Bharti Joshi (bharti.joshi@simmons.edu)

[edit] Schedule/Timeline

  • Download and understand Aurora Software DONE
  • Verify access to the Simmons server (still some technical problems)
  • Coordinate level of granularity (work, image) with other committees - Still a few questions
  • Determine workflow DONE

Next steps:

  • Map the descriptive and preservation metadata to the database fields DONE
  • Import the creator and subject lists into Aurora DONE
  • Customize the drop-down menus for easier workflow DONE
  • Begin data entry DONE
  • Determine best way to transform data into HTML pages DONE

[edit] Meetings and Minutes

[edit] Notes

Some preliminary notes on AuroraDL

Structure

Aurora divides the data into several sections: Works, Images, Agents, Subjects, Notes, and a few others.

Something for the class to consider: At what level should we place the division between Work and Image? It looks like we'll be working with four levels of granularity: the scrapbook; scrapbook page; item; images (more than one for multiple-page items). See below for what data constitutes Work and Image.


Data fields

Works:

  • Title Type Set (Title, Publisher, Place, Year)
  • Materials Type Description (Description, physical characteristics, style/period
  • Geographic source descriptors (mostly for architectural objects)
  • Work-to-work relationship

Images:

  • Object data (file name, resolution, size, thumbnail, etc.)
  • Image content panel (Image title, Style/Period, Image-Work relationship, etc.)
  • Image production (Name of scanner/photographer/etc. and date)

Agents:

  • Choose from a list of Agents or create new. Assign role.

Subjects:

  • Choose from user-provided thesauri. Assign subject source and type.


Workflow

Images to be processed are stored in a folder (hierarchy viewable from the interface). Work can be done either horizontally or vertically. A horizontal approach would consist of:

  • catalog the Work and saving
  • Work reference ID is automatically assigned and a datafile is saved on the server
  • Choose an Image and associate it to the Work
  • catalog the Image and save; Image ID assigned & datafile saved
  • add Agent and Subject sets to the active image

Work can also be done vertically: one Work record can be applied to an entire folder of Images; Images can be processed one after the other, then Subject sets assigned to each image, etc.

End user

We haven't had access to the GUI yet, but features pointed out in the manual include:

  • Basic "keyword" search
  • A detailed advanced search
  • The ability for the user to choose from several different display options, with different interactive features
Retrieved from "http://gslis.simmons.edu/wikis/lis462/AuroraDL_Committee"
Personal tools