The Document Library in Share is probably the most comprehensive Surf page (note that it has not yet been converted to Aikau) in the whole application. You will have a number of extension points available so you can customize according to customer requirements.
The following list describes the different Document Library sub-extension points:
- Actions - The document library page has lots of actions that you can use to manipulate the content you are looking at, whether it is a file or folder, such as Download. It is also possible to add your own actions so you can process content in a domain specific way.
- Indicators - A content item in the Document library can have zero or more so called indicators, they can be used to denote certain states of the content, such as a file has been emailed. You can add your own indicators, they would typically be used together with an action.
- Metadata templates - Whenever you view a list of folders or files in the Browse view there is a small number of metadata properties displayed. You can define custom metadata templates to control what metadata is displayed for a specific content type.
- Views - When you are browsing the Document Library it is possible to select how to view it. By default the Detailed View will be active, but you can also select from the following views: “Simple”, “Gallery”, “Filmstrip”, “Table”, “Audio”, and “Media”. If none of these views fit your needs it is possible to define custom views.
Most of these sub-extension points are actually part of the Share Configuration extension point as they are applied via XML configuration in share-config-custom.xml (for more information, see Share Configuration). It is really just the Actions sub-extension point that will involve coding.
The following picture shows an example of how the Document Actions looks like in the UI:
If you are viewing a Folder instead of a file you will be looking at Folder Actions.
There are a number of ways in which these Document Library actions can be implemented. The following picture illustrates:
So an action can be implemented as a client side JavaScript function that calls a repository action or a web script via AJAX. And an action can also just link directly to an existing Share Page. And finally, it is possible to have an action link to an external page.
Next picture shows you the views:
The Detailed View is currently active and the drop down to the right shows you the other available views. An indicator looks like this for a file:
In this case a workflow was started, and there is a little icon indicating that this file is part of a workflow. The default metadata template for files looks like this: