USE CASE: Photo library

[kcoyle]

Creator: Karen Coyle

Problem statement

I have a small collection of photographs that are used by the teaching staff in the Art department. These will not need to be fully cataloged in the way that the library's books are cataloged, but the professors need to be able to find them by artist, work title, place (mainly for buildings or public art), and genre. The staff cataloging these items will be students in the department, and they will get minimal training. I need to create a small schema to use for this work. I prefer to have the schema directly populate a web form, including eye-readable labels for the data elements and some short instructions for each element that tell the catalogers what is expected for that field.

Stakeholders

Faculty using the photos; student workers creating the data

Links

''Optional link list to documents and projects this use case refers to''

Requirements

1. Must allow the inclusion of labels and instructions

Comments

This is a sample use case, based on the template at usecase.md

[nichtich]

Better put this as file into the git repository in a use-cases directory?

[nishad]

Issues are a smoother workflow, especially with labels. Maintainers can move them to the repo, once the entry is accepted and close the osse. This will reduce the number of pull requests.

Also, we should consider temples as well.
https://help.github.com/en/articles/about-issue-and-pull-request-templates

_{Sent with GitHawk}