Introducing the Digital Repository for Museum Collections (DRMC)

  • View
    1.488

  • Download
    1

Embed Size (px)

Text of Introducing the Digital Repository for Museum Collections (DRMC)

DRMC

DRMCIntroducing the Digital Repository for Museum CollectionsDan GilleanJess Garca Crespo

BACKGROUND2011 - 2013

BACKGROUNDTMSarchivematicaSTORAGEDAM

MANAGER

BACKGROUNDTMSarchivematicaSTORAGEDAM

MANAGERRELATIONSHIPSDEPENDENCIESSEARCH / BROWSEREPORTINGANALYTICSFIXITY MONITORING

FRBR + DIGIPRES

BACKGROUNDRFP ISSUED: 2013329FUNCTIONAL REQUIREMENTSUSE CASES

BACKGROUND329FUNCTIONAL REQUIREMENTSUSE CASES

RFP ISSUED: 2013

DRMC Team

Jess Garca CrespoLead DeveloperDavid JuhaszProject Manager

Dan GilleanDomain analysis; Design

Mike CantelonDeveloperMisty De MeoDeveloperJos Raddaoui MarnDeveloperHeather AndersonDeveloperArtefactual is a small open source web development company of about 16 peopleOur main projects are AtoM, a web-based application for standards-based archival arrangement, description, and acess; and Archivematica, a web-based digital preservation system.

Weve had 7 members of our team focused on development of the DRMC, with participation from other team members at various points.

David Juhasz has acted as Project Manager throughout this project, While Jesus Garcia Crespo is our Systems Architect and Lead DeveloperI have been responsible for Domain Analysis and User Interface designMike Cantelon has done both Front and back end development throughout the projectMisty De Meo has built our fixity checker app, and worked on Archivematica integration and developmentJose Raddaoui Marin has developed much of the Elasticsearch architecture and REST endpointsHeather has done a lot of the front-end work in Angular

820132014JUNJULAUGSEPTOCTNOVDECJANFEBMARAPRMAYJUNANALYSISPROTOTYPINGDEVELOPMENTSITE VISITUSABILITY STUDYTECHNICAL ADVISORS MTGUSABILITY STUDYDEVELOPMENT TIMELINE

From use casesTo UX flowchartsThis slide depicts an example of how the process followed from phase one to phase two.

The image in the top right depicts one of the use cases that MoMA had outlined as a requirement for DRMC functionality in essence, a conservator searches for a work, finds it and navigates to it, and then browses the files contained within an associated AIP.

The first thing we did was to take these text-based use cases, and transform them into workflows shown in the bottom left-hand corner. This helped us to understand the use case visually, and to be able to determine for each task what steps the user would take, and what corresponding actions would be performed by the application. Based on these, we could then determine how many wireframes we felt would be necessary to illustrate the interface as each action took place.

The top images in the middle and on the right show two examples of the wireframes produced from this workflow the first depicts a sample of the search results, while the image on the right shows an example of the digital object browser used to explore files contained within an AIP.

Below are images of the application as it was a month ago mid development. Many elements have been developed almost exactly as they were in the original wireframes, while other elements have changed based on the flexibility of the agile model testing, feedback, evolution. We felt that this combination of approaches that is, a long and well-considered planning phase, combined with an agile and flexible development methodology has given us a strong base from which to work, while still retaining the ability for us to adapt and account for new ideas. 10From UX flowchartsTo wireframes

This slide depicts an example of how the process followed from phase one to phase two.

The image in the top right depicts one of the use cases that MoMA had outlined as a requirement for DRMC functionality in essence, a conservator searches for a work, finds it and navigates to it, and then browses the files contained within an associated AIP.

The first thing we did was to take these text-based use cases, and transform them into workflows shown in the bottom left-hand corner. This helped us to understand the use case visually, and to be able to determine for each task what steps the user would take, and what corresponding actions would be performed by the application. Based on these, we could then determine how many wireframes we felt would be necessary to illustrate the interface as each action took place.

The top images in the middle and on the right show two examples of the wireframes produced from this workflow the first depicts a sample of the search results, while the image on the right shows an example of the digital object browser used to explore files contained within an AIP.

Below are images of the application as it was a month ago mid development. Many elements have been developed almost exactly as they were in the original wireframes, while other elements have changed based on the flexibility of the agile model testing, feedback, evolution. We felt that this combination of approaches that is, a long and well-considered planning phase, combined with an agile and flexible development methodology has given us a strong base from which to work, while still retaining the ability for us to adapt and account for new ideas. 11

From wireframes To prototypesThis slide depicts an example of how the process followed from phase one to phase two.

The image in the top right depicts one of the use cases that MoMA had outlined as a requirement for DRMC functionality in essence, a conservator searches for a work, finds it and navigates to it, and then browses the files contained within an associated AIP.

The first thing we did was to take these text-based use cases, and transform them into workflows shown in the bottom left-hand corner. This helped us to understand the use case visually, and to be able to determine for each task what steps the user would take, and what corresponding actions would be performed by the application. Based on these, we could then determine how many wireframes we felt would be necessary to illustrate the interface as each action took place.

The top images in the middle and on the right show two examples of the wireframes produced from this workflow the first depicts a sample of the search results, while the image on the right shows an example of the digital object browser used to explore files contained within an AIP.

Below are images of the application as it was a month ago mid development. Many elements have been developed almost exactly as they were in the original wireframes, while other elements have changed based on the flexibility of the agile model testing, feedback, evolution. We felt that this combination of approaches that is, a long and well-considered planning phase, combined with an agile and flexible development methodology has given us a strong base from which to work, while still retaining the ability for us to adapt and account for new ideas. 12REUSING AtoM

DRMCAuthentication / AuthorizationTaxonomiesSearch capabilitiesArchivematica integrationArchival descriptionsAuthority recordsFunctionsArchival institutionsAdvanced searchAccessionsPhysical storageetc

Authentication / AuthorizationTaxonomiesSearch capabilitiesArchivematica integrationAIPsDashboardContext browserArtwork recordsSupporting technology recordsReportsFixity checksetc

DRMC STACKSERVERBROWSERHTTP APIDRMC

AngularJS

Graphic by Ben Nadel

DECLARATIVE DATA BINDING

Most recent fixity checks

  • AIP UUID {{ item.aip.name }} {{ item.aip.uuid }}
    Duration: {{ item.duration }} seconds
    {{ item.error }}

DECLARATIVE DATA BINDING

Most recent fixity checks

  • AIP UUID e1d966c6-baf5-4f2c-9712-eb5686d40892Duration: 1m 32s
  • AIP UUID 16df4e80-a9f0-4f3c-906c-ba412c8dd9d3Duration: 8m 14s
  • AIP UUID 58e7a7ac-8763-46f3-937f-753918110dafDuration: 7s

CONTEXT BROWSER

CONTEXT BROWSER

ARTWORK RECORD

ARTWORK RECORD

DIGITAL OBJECT BROWSER

DIGITAL OBJECT BROWSER

DASHBOARD

DASHBOARD

ARTWORK BROWSE

AIP BROWSE

REPORTSWHATS NEXT?RebrandPublic demo siteAbstract MoMA-specific codeOpen source angularJS appPrep websiteRelease API documentationCreate screencastsFind development partners

INTERESTED?

info@artefactual.comThanks!