Historical periods controlled vocabulary

Needed by whom and when

Basic statements about who needs the functionality and by when.

PAHMA: Some functions needed by when?

Overview

PAHMA (and presumably other collections) have objects that are associated with historical events or periods. Beyond basic associations, they would like the system to have intelligence about historical events and be able to associate other objects in the collection that are dated to that period but not specifically associated with a historical event.

Note: In a conversation on October 20, 2010, Michael Black said this was not a high priority.

Question: Is this a question about specific events or rather periods or eras?

Question: What is the information schema for historical events (name, start date, end date, description, notes)?

User stories for definition

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

Historical events controlled vocabulary: User can manage historical events or periods in a controlled vocabulary.

Historical events controlled vocabulary: User can associate objects with historical events.

Historical events controlled vocabulary: System will have some intelligence to associate historical periods with dates and facilitate searching the collection.

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