HTTP Authentication

Title (Goal)	Support for HTTP authentication and access policies
Primary Actor	Administrator, Harvester
Scope	Data access
Level	High
Story	Repository object information should be made available for harvesting and integration as soon as possible. However, some harvesting clients may have different permissions for downloading records or accessing particular sets. HTTP authentication should provide a OAI-PMH compatible mechanism to restrict access if necessary.

Dynamic Sets

Title (Goal)	Support for dynamic OAI sets
Primary Actor	Repository Manager, Harvester
Scope	Data access
Level	High
Story	It should be possible to define an OAI set by using Fedora object properties and predicates. Objects that fit to the defined pattern should be disseminated as members of the so defined sets.

Title (Goal)	Support for configurable OAI deletion policies
Primary Actor	Repository Manager, Harvester
Scope	Data access
Level	High
Story	OAI specification describes three tracking levels for record deletion: no, persistent and transient. While NO and TRANSIENT do not provide any useful information about deleted records, PERSISTENT explicitly states the deletion of a previously existing record and thus helps to keep a harvesters database update to date. The repository should allow to configure the deletion behavior according to OAI specification.

Title (Goal)	Support for multiple metadata formats beyond oai_dc
Primary Actor	Repository Manager, Harvester
Scope	Data access
Level	High
Story	The repository is able to store and disseminate multiple XML based metadata formats. This formats should also be accessible in OAI harvesting. Access to some metadata formats may be restricted via HTTP Authentication.