WMS : Democratizing Data

  • View
    34

  • Download
    1

Embed Size (px)

DESCRIPTION

WMS : Democratizing Data. WMS Workflow Management System for Ru core Rutgers Community Repository. WMS Overview Grace Agnew. WMS : Democratizing Data. WMS – What is it?. Tool for ingesting digital objects and metadata User centered :Administrator and team member “views” - PowerPoint PPT Presentation

Text of WMS : Democratizing Data

  • WMS: Democratizing DataWMS OverviewGrace Agnew

    WMS

    Workflow Management Systemfor Rucore

    Rutgers Community Repository

  • WMS What is it? Tool for ingesting digital objects and metadata User centered:Administrator and team member views Enables community repository development:distributed participationanyone with web access Enables standardization and customization

    WMS OverviewGrace Agnew

    WMS: Democratizing Data

  • WMS What is it?

    Supports Preservation: perpetual access Data model provides management and access to object throughout its lifecycle Analog ---- Digital--?? standard support Flexibility for the future agnostic to schemas, object formats, WMS: Democratizing DataWMS OverviewGrace Agnew

    And the ways people look for and use information

  • WMS: Democratizing DataRole in the Repository

    WMS OverviewGrace Agnew

  • RUcore - How it Works

    DigitalObjectRepository(Fedora)

    Digital Object Ingest

    Fedora Repository Service

    User, Collection, & Preservation Services

    E-Journals

    NJ DigitalHighway

    Dissertations

    User Input

    Metadata andArchival masters

    RUCORE &Application Portals

    April 3-4, 2006

  • WMS: Democratizing DataDevelopment and DeploymentMetadata WGCollaborators (NJDH, MIC, Faculty)WMS Project ManagerProgramming TeamSoftware Architecture WGRUCore Steering CommitteeWMS OverviewGrace Agnew

  • WMS: Democratizing DataRUcore Data ModelMary Beth Weber

    RUcore Data Model

  • WMS: Democratizing Data

    Event based = When an object interacts with an agent or place at a specific point in time, an event occurs in the lifecycle of the object. Event = Professor visits Italy and takes digital photographs. Cataloger creates metadata for digitized images. Researcher locates images, uses them for book and lecture.

    RUcore Data ModelMary Beth Weber

    How the Data Model Works

  • WMS: Democratizing Data

    Easy to understand and interpret by both information managers and usersContext independentShould be a representation of living dataSupports management and preservation of dataRUcore Data ModelMary Beth Weber

    Best Practices for Data Models

  • WMS: Democratizing DataPreservation MetadataStores information that supports preservation decisions/actionsDocuments preservation processes, such as data migrationsDigiProvSpecifies the changes an object/file has undergone since its digital birth.

    METS Support Access for PreservationMary Beth Weber

    METS Preservation Support

  • WMS: Democratizing DataStandards: MODS METS - PREMISFormats: Text Audio Still images Moving images Simple and ComplexMetadata: Descriptive AdministrativeEvent-based

    Innovation and CollaborationRhonda Marker

    Innovations

  • WMS: Democratizing DataSave timePromote consistency and accuracy Build on local practices

    Innovation and CollaborationRhonda Marker

    Templates and mapping

  • WMS: Democratizing DataPartnership with Graduate School of New BrunswickMap -- Dublin Core and MARC21

    Innovation and CollaborationRhonda Marker

    Electronic Theses and Dissertations

  • WMS: Democratizing Data

    ETD Input ScreenRhonda Marker

  • WMS: Democratizing Data

    Metadata MappingRhonda Marker

  • WMS: Democratizing DataA digital object and metadata tool for Fedora or other digital repository systemsHandles digital object upload and creationHandles metadata manipulation (create, import, export, convert between schemas)Scalable, flexible and expandableEasy to useWMS Design and ArchitectureYang Yu

    Some Design Issues

  • Database drivenXML - data model and data carrierModularization of functionality componentsObject oriented application design Context driven data entry interfacePHP/MySQLSome Design DecisionsWMS: Democratizing DataWMS Design and ArchitectureYang Yu

  • WMS: Democratizing DataWMS ComponentsWMS Design and ArchitectureYang Yu

    Digital File ModuleMetadataModuleFile SystemCommon Data ObjectInterfaceUSER

    INTERFACE

    ImportModuleExportModule

  • WMS: Democratizing DataWMS DatabaseWMS Design and ArchitectureYang Yu

    RULMODSCollection MgmtControlled TermsFile MgmtMETS

  • WMS: Democratizing DataWMS Digital File ManagementWMS Design and ArchitectureYang Yu

    System generatespresentation files(pdf, jpeg, etc.)File SystemDigital Object(HTTP upload, CD, FTP, etc.)AssociatedMetadata

  • WMS: Democratizing DataWMS Metadata ProcessingWMS Design and ArchitectureYang Yu

    Task HandlerCommon Data ObjectInterfaceUSER

    INTERFACE

    Import Non-RUCore metadataXSLTConversionMappingUtilityExportDatabaseManager

  • WMS: Democratizing DataCreate collection objectCreate resource objectCreate templateUpload digital fileCreate presentation filesCreate metadata recordExport to repositoryImport xml from User Applications (example ETD Student input)

    WMS FeaturesKalaivani Ananthan

    What can WMS do?

  • UserOrganizationCollectionProjectTemplateProject SetupDigital File Upload

    Still Images Pdf Jpeg Djvu OCR for textCaptured Audio MP3

    Create Presentation Files

    Descriptive MetadataAdministrative Metadata Source Metadata Technical Metadata Rights Metadata

    Create Resource Record Export

    Digital Object

    RepositoryWMS: Integrated Workflow for Digital Objectshttp://mss3.libraries.rutgers.edu/workflow

  • WMS: Democratizing DataSoftware may be bug-free yet still be unusable2 ways the GUI obstructs users1. Sets Incorrect Expectations2. Sets Ambiguous ExpectationsWMS UsabilityShaun Ellis

    What is Usability?

  • GUI design is a processSome hand-holding is needed in complex systemsRead The Fabulous ManualWMS: Democratizing DataWMS UsabilityShaun Ellis

    Designing for Usability

    New roles for imaging specialists and metadata managersConsulting and advising collection partners

    Each project team includes collection owner, project manager, and metadata managerWMS allows, and we encourage, the creation of templates for metadata creation. Templates save time creating metadata records. They also promote consistency in all the records created for a project, and of course they also ensure more accurate record creation in terms of both completeness and correctness.

    The metadata managers also map to and from the native metadata that might have been used in a local metadata application to the METS/MODS schema that we use in the WMS. We have successfully mapped to Dublin Core, MARC, and PBCore.

    The Electronic Theses and Dissertations collection is a good example of the new roles for collaboration. A group of programmers, project managers, and catalogers worked together as a team to develop the ETD workflow and standards. The leadership of that group is working with key staff in the Graduate SchoolNew Brunswick to build their requirements for graduate students into the ETD workflow.

    The software we are using for the local ETD application bases the metadata on Dublin Core. We have mapped those elements into our METS/MODS schema. We also will export the metadata to our local online catalog in MARC, so the METS/MODS metadata has been mapped to MARC. The ETD information sheet that the graduate student completes and send to the Graduate School gathers much useful information that can be used in the WMS. It includes the candidates name, the dissertation title, page numbers of the bibliography, the language of the dissertation, and so forth.The metadata manager, in a new role for catalogers, plots the metadata elements used by the collection partner, here expressed as Dublin Core.

    These elements are mapped to the METS/MODS elements used in the WMS, and in this case also the MARC fields and subfields. This map is used by the programmer/analyst to export the ETD metadata record and the digital file for upload into the WMS.

    We have been able to accommodate all of the metadata schemas weve encountered so far, and also the data requirements of our collection partners who never created metadata or who never previously cataloged their collections. Our ability to adapt the WMS to a wide variety of collections is due in part to the flexibility of the METS framework but mostly to the extensive development of the metadata model in the WMS.