The configuration layer is a layer designed to assist in the extensibility of the digital library. The aim of the configuration layer was to provide a mechanism that allowed for the configuraion of available digital library services dependent on which archive was being explored. Each archive would be required to have an indicator of its expected services.
In addition, the configuration layer is to allow for the introduction of a new archive into the entire digital library without the need to re-implement the system to accommodate for the new archive.
Figure 1: System architecture from the perspecitve of the configuration layer
The image indicates the entire system architecture and the involvement of the configuration layer. The configuration layer, here, is represented by the properties file. It is evident, as per the image that the system is designed in a way such that there is one landing page that is accessed on accessing the website. This landing page then has links to navigate to the necessary archives. The archives each have distinct home pages and all point to the same instance of the services provided. An example of the properties file can be seen below.
Figure 1: Upload interface flow diagram
The configuration layer saw a two fold implementation:
The first part of the configuarion layer implementation involved the creation and addition of a new archive to the system. This was done by automatically generating any files required for the existance of an archive within the digital library.
The archive configuration process involved:
- the generation of a properties file
- the generation of the landing page for the application to include a navigation option to the new archive
- a blank home page with the generic navigation bar indicating the services available would be generated for the new archive
The second element of implementation involved the management of the archival services dependent on which archive was being accessed. The toggling of these services is governed by the properties file discussed.
Evaluation and ResultsThis layer was assessed using Junit test cases. The tests involved automatically generating the expected files and interrogatng the values contained to see if the generation had occurred successfully.
ConclusionsThe configuration layer successfully toggles the services for each archive and provides a mechanism for the introduction of a new archive by a user with technical experience.
Future work for the configuration layer could involve being able to add additional services to the digital archive. Ensuring extensibility in terms of the addition of new archives but also in terms of new services.