Design Team to provide UI/UX and Functional Requirements for Modeling

[azaroth42]

Responsible: @ggeisler @hannahfrost Accountable: Consulted: Informed: @azaroth42 @no-reply

As survey analysis and further discussions take place, any design decisions must be fed to the modeling group to ensure that there is sufficient information available in the system to enable those requirements.

[anarchivist]

@ggeisler @hannahfrost Is this something we can either shoot to have done before or during the DRS face-to-face meetings in La Jolla?

[hannahfrost]

@anarchivist We can start to work on this in La Jolla. One hang-up is that neither @ggeisler nor I know how Sufia 7, our starting point, works in this regard. That UI is still under development. But I'll start to write up come user stories for images and have them to share for our discussion

[mjgiarlo]

I'd be happy to help with that, @hannahfrost @ggeisler

[hannahfrost]

:+1: @mjgiarlo Thanks.

[hannahfrost]

@azaroth42 @no-reply Here is a document with three user stories for the scanned postcard content type. Please let us know your feedback. Are these useful for data modeling?

https://docs.google.com/a/stanford.edu/document/d/1nWlUriv0tp3t8asmuoC_VKph5Rwa-shwnntExRlArZo/edit?usp=sharing

[azaroth42]

Yes thanks @hannahfrost :)

Question that arises from 1a: Is transcription of the content depicted in the image required / nice to have / optional? There's a lot of UI/UX issues around viewing of transcriptions, and a lot of variety around the recording of it -- are there word level coordinates? Line level? Page/Image Level? Or is there just a single file that has the entire text of the object?

[hannahfrost]

@azaroth42 We are thinking something less complex: transcription in a metadata note field. See how VCU has done it (in CONTENTdm, BTW): http://dig.library.vcu.edu/cdm/singleitem/collection/postcard/id/316/rec/56

This is not to say that separate file with transcription is not desirable, but not as a primary use case

[hannahfrost]

@azaroth42 @no-reply So can you confirm that we struck the right level of detail in the use case?

[anarchivist]

Notes from 2/3/2016

• Start to identify use cases, e.g. "once the postcard is in the repository, what can we do with it?"
• Clarify on transcription - what is the intent and how will it be used? Is it a simple property with a string literal value, or does it represent another repository resource?
• Diversify image examples beyond postcard
  • photograph
  • postcard
  • letter
  • book
• What are the base assumptions?
  • Descriptive metadata lives on a top level object
  • 1..n objects hang off that, but unclear about whether e.g. a recto/verso would to have their own description
• Identify potential serialization
• Consider a "top-down" UX-focused analysis process, which focuses on user interactions
  • analyze existing metadata input processes
  • analyze discovery processes
  • "if i'm managing X, what do i need to do to manage X in hybox"
• Could also consider doing a text-based entity-relationship analysis (or developing an ERD)
• Scope decisions
  • for now only capture workflow concerns about getting metadata into the system and related to discovery
  • identify access controls as they come up but DMT operating under assumption that WebACL will handle this
  • ordering in scope
  • identify whether people/places/etc. are entities w/ their own MD and independently discoverable or managed
  • identify things that are part of the minimum viable product (or minimum compelling product)

[hannahfrost]

@azaroth42 @no-reply Following our helpful discussion in San Diego, the DRS team worked further on the user scenarios.

We modified the postcard scenarios, and added one each for photograph, letter, and book. Have we provided you with what you need for the image-based data modeling work? Please review and let us know your questions.

Again, the link: https://docs.google.com/a/stanford.edu/document/d/1nWlUriv0tp3t8asmuoC_VKph5Rwa-shwnntExRlArZo/edit?usp=sharing

[azaroth42]

Ack. Will get to this (and other HyBox) next week.