search

hybox / project-planning

Project planning and todos for HyBox
2 stars 0 forks source link

Product Team to decide on first Content Types #51

Closed azaroth42 closed 8 years ago

azaroth42 commented 9 years ago

Responsible: @tomcramer @hannahfrost @mjgiarlo @anarchivist Accountable: ? Consulted: ? Informed: @azaroth42 @no-reply @ggeisler

In order to make progress with modeling content and generating UI designs, the modeling and UI groups needs to know what the first basic content types to be worked on are. These must be more detailed than "Video" or "Image" in terms of intellectual content, and should include use cases rather than just labels.

Proposed examples of useful patterns:

mjgiarlo commented 9 years ago

@azaroth42 @no-reply @ggeisler @hannahfrost @tomcramer @anarchivist

I'm somewhat less opinionated about #51 (vs. #50 and #52). My inclination is that the two included examples above (scholarly text and photograph) are likely quite good to include in a top 3 or top 5 of supported content types, and thus seem like safe bets to model. That said, I think we should not guarantee that the HyBox MVP will support them -- but they should be sufficiently well defined such that if we do have the resources, we can develop support based on existing modeling & UI group work.

azaroth42 commented 9 years ago

:-1: on this being ready. What we need is a decision for the first (and/or only?) content types. An inclination that that two examples are maybe in the top 5 and maybe a waste of time to work on depending on resources seems underspecified to me.

mjgiarlo commented 9 years ago

@hannahfrost @anarchivist @tomcramer Reflecting what I just heard in the room here in NC... what if we say that Images/photographs are our top priority at this point and punt on other modeling at this time?

azaroth42 commented 9 years ago

These must be more detailed than "Video" or "Image" in terms of intellectual content

So ... photographs? There's a pressing need for photograph models in institutional repositories rather than scholarly texts?

azaroth42 commented 9 years ago

Don't get me wrong, if that's the decision I'm happy to run with it :smile_cat: It is just surprising that we want (for example) a mediated deposit workflow, metadata mapping and batch ingest for just photographs.

hannahfrost commented 9 years ago

@azaroth42 The Design Requirements and Specs team discussed this quite a bit today in Raleigh and meanwhile there is now this document: https://docs.google.com/a/stanford.edu/document/d/1H29JQrmGr27BUgjKn5JRvFwiiP7mDEBcAHTAwtcIrYo/edit?usp=sharing. We may have more discussion tomorrow and it will be useful to discuss further with you next week. Looks like you will be in the office?

azaroth42 commented 9 years ago

:+1: Looks great :) and yes, am in next week.

hannahfrost commented 8 years ago

Ready to declare the first two content types: (1) Image-based work with ordered files: Archivist submits scanned postcards as pairs of images (front and back) with basic metadata derived from spreadsheets (2) Multi-file work with unordered files: Researcher submits tabular data file with associated README, scripts and codebook to supplement a journal article

All the content type work is being documented here, please have a look: https://docs.google.com/a/stanford.edu/document/d/1H29JQrmGr27BUgjKn5JRvFwiiP7mDEBcAHTAwtcIrYo/edit?usp=sharing

Comments, discussion is invited. If the modeling team can work with this, then I'll close the ticket.

mjgiarlo commented 8 years ago

Needs review from @azaroth42 @no-reply!

@hannahfrost We should revisit our FAQ about content types once this ticket is closed, I suppose. Do you want to take that, or shall I?

hannahfrost commented 8 years ago

@mjgiarlo I'm happy to keep the content type FAQ updated. Thanks!

hannahfrost commented 8 years ago

The content type prioritization work is well underway. See #54 for more detail on functionality expressed in user stories. While that work will be ongoing, the essence of the work expressed in this ticket is fulfilled.