Museum-only objects not shared with public

Needed by whom and when

Basic statements about who needs the functionality and by when.

PAHMA and UCJEPS: Some functions needed by the time they move to CollectionSpace as their production system

Overview

PAHMA and UCJEPS need to be able to mark some objects in their collection as non-shareable.  They should not show up when a web interface for public viewing is provided in CollectionSpace.

Question: Should these objects be hidden from certain user roles (e.g., student data entry role)?

Question: Should this be the data view that other interfaces to the data use (e.g., via the services layer)?

User stories for definition

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

Museum-only objects: User can mark an object so that it is not findable or viewable through a public interface to the collection.

Museum-only objects: User can mark an object so that it is not findable or viewable to certain CollectionSpace roles.

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