Research visits

Needed by whom and when

Basic statements about who needs the functionality and by when.

PAHMA: This is important eventually but probably not required by the time they move to production mode.  UCJEPS would like this too.

Overview

PAHMA and UCJEPS would like to record what people looked at what objects in their collections and what their interactions were.  They would also like to be able to facilitate research visits by creating lists of objects that visitors are coming to see (e.g., name, storage location, handling notes).  This is not a very high priority.  It does seem to follow the Use of Collections process from Spectrum.

This can help the museum track their education contributions.

Question: What is the schema for a research visit?  Person, organization, date, purpose, note?

User stories for definition

Please feel to rewrite these or eliminate completely!  Then move to the prioritized headings below.

Research visits: User can identify that object has been subject of a research visit.

Research visits: User can facilitate research visits by preparing a visit list for a set of objects.

Prioritization of user stories

As definitions and priorities are clarified, the user stories above should be moved into relative order below.

Must have for 1.x-MUSEUM (when they go live in system)

Placeholder for required functionality.  As a general rule, functionality that you need and use now should go here or where you have existing data.  However, this is up to the museum.  We will have to balance requirements against resources and timelines.

Placeholder

MUSEUM could wait six to twelve months

What could wait?  These will be re-prioritized at a later date.

Placeholder

MUSEUM would like to have this eventually

These are nice to have but not a near term requirement.

Placeholder