Page History

...

• Entering resources is done using forms tailored to customers' needs or directly from customers' information systems through interfaces. It is possible to determine user rights and entry stages in the system, which allows management of the materials' passage through the entry stage towards a finished online publication. For example, it is possible for researchers and students to enter and describe their materials on their own, after which the staff of the organisation will check and revise it further before the final online publication.
• Customers are provided support in resource management in the form of tools for editing, mass-editing, limiting user rights, and statistics functions, as well as reusing materials and transferring them to other systems. Customers have complete control over their materials throughout their lifecycle. For example, customers always have the opportunity to copy and transfer their materials to another system, if they want.
• Online resources are retrievable with tailored browsing and search functions. For text publications, such as PDF files, the search will also cover the full text in addition to metadata. The Solr search engine's syntax  enables enables both easy-to-use and more specific searches within the publication archive or from other systems through user interfaces. This means that searches can for example be integrated into an online store or a search portal. Our repository platform supports OAI interfaces, such as OAI-PMH and OAI-ORE, through which materials can be harvested into search portals, such as Finna, Base, OpenAIRE and Core. The resources are available to be indexed by search engines, for example Google indexes full texts in addition to metadata. The user interface makes it easy to share the materials on social media. It is always possible to get a permalink for the published materials, which will ensure that the URL of the resource will remain the same even if the record's platform or service provider changes in the future.
• Conversion services are needed when resources are added retroactively to the repository from and old system or from a system to be integrated. Conversion is an individual process, which is always planned in cooperation with the customer. Almost without exception, conversions also entail a need to correct deficiencies or inconsistencies originating from the old systems. Consequently, conversion often also entails harmonisation and enrichment, as a result of which resources can be found online more easily. Our repositories use a Dublin Core (DC) metadata format. We will help the customer to select DC metadata fields suitable for the resources, in order to make them as uniform as possible with the repositories so that the desired search and browsing needs can be met.

...