Users and Guests will have the same user interface, the difference lies in Component access restrictions, and Administrators will have a separate user interface in the Application. The Application will not provide Maintenance with a user interface, any kind text editor is suitable. The provided user interface will be web based, and the language used in the interfaces will by default be English but replaceable with other languages.
This section presents the functions of the Application. For more information about the user functionallity, see the section called “Requirements of the Application”.
A user can loggin to the Application. This is done by authenticate a user by a username and password. Authenticated users are associated with roles according to the current user configuration, unathenticated users are associated with a special Guest role.
An authenticated user can logout form the Application. This is done by removing the associated user information form the Application.
An Administrator can add a new portfolio to the Application. This is done by assigning a User as Owner of a Portfolio Component, adding metadata about the Owner and a initial root structure to the repository.
An Administrator can remove an existing portfolio from the Application. This is done by removing the metadata associated with the Owner of the Portfolio Component and Material Components in the organization structure of the Portfolio Component. See the section called “Remove component” for more on removing Material Components.
An Administrator can make a backup of a portfolio. This is done by writing all metadata associated with the Owner of the portfolio, the portfolio organizational structure, metadata about Components in the organization and content of any File Components in the organization to a ZIP-file.
An Administrator can restore a portfolio from a backup. This is done by replaceing all metadata associated with the Owner of the portfolio, the portfolio hierarchical structure, metadata about Components in the hierarchical structure and content of any File Components in the hierarchical structure in the repository from a backup.
A User can add new Material Components in a organization. This is done by adding a new item to the organization and associating metadata about the new Component with the item. For File Components is the file content uploaded to the repository an a reference to the uploaded file is added in the Components metadata.
A User can remove Material Components from an organization. This is done by removing the corresponding item, and associated metadata, from the organization. If the Component has a reference to a uploaded file, and no other Component has a reference to it, is the uploaded file also removed from the repository. Removing a Folder Component implies that Components included in the organzation also are removed from the repository.
A User can open, or access, a Component. This is done by presenting views of hierarchical structutures for Portfolio Components and Folder Components, downloading file contents for File Components, redirecting the browser to URLs defined for URL Components or presenting views of metadata for Person Components.
A User can change the organization of Material Components in Folder Components. This means that a Component can be moved, copied or linked between Folder Components, also can the order between Components in a Folder Component be changed.
Moving a Component from one Folder Component to another Folder Component just means that the corresponding item is removed from the source Folder Component and inserted last in the organization of the receiving Folder Component.
To copy a Component between Folder Components means that a new item is added to the organization of the receiving Folder Component. All metadata associated with the source Component are copied and associated with the new item. For a Folder Component are all Components included in the organization also copied. To copy a File Component only means that metadata and the reference to file content is copied, the file content does not need to be copied since the content is accessed through a reference.
To create a link in a Folder Component to a Material Component in a second Folder Component means that a new item is added to the organization of the destination Folder Component and assigned a reference to the metadata associated with the Material Component.
A User can change the metadata associated to a Material Component. Each type of Component has its own set of metadata associated to it. The editor module resolves which metadata editor to use for each type of Component.
A User can view the metadata associated to a Material Component. Metadata for each type of Component will be presented in dedicated web pages.
A User can query the Application for Components matching a set of criterias. The User then receives a list of Components with a subset of metadata, from which individual Components can be requested. The User may specify, in the request, how many Components the Application should present on each page.