User statistics

Needed by whom and when

Basic statements about who needs the functionality and by when.

PAHMA: Not needed by 1.x-PAHMA, but it would be good to have user statistics eventually.

Overview

Museum administrator or system administrator can capture some user statistics (login, logoff, transactions saved). 

Question: What are the statistics that should be captured in this report beyond login date, logoff date, number of transactions saved?

User stories for definition

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

User statistics: System administrator can run a report showing statistics about user or users (login time, logoff time, number of transations saved).

User statistics: CollectionSpace user with sufficient rights can run a report showing statistics about user or users (login time, logoff time, number of transations saved).  Question: What role should be able to run this report?

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