## 2 Literature Review  
The logical architecture of many digital repositories consists of several parts. Usually, there is a part responsible for the business logic (platform or engine). Another one is responsible for data preservation (file systems or databases). The last one is used to interact with users within the web browser window (access application). These parts are loosely coupled and often run as independent web services. The communication between them goes through the endpoints with well-defined application programming interfaces. In Table 1, some of the existing implementations of digital repositories are listed, including platform only and fully featured repositories. All are open-source software-based. A more detailed comparison of selected repositories is given in [4] (a bit outdated, but still valid) while custom implementations are in the focus of [5,6]. In scientific or business-related fields, the term digital repositories (DRs) is often associated with institutional repositories (IRs)--understood as sets of services for the management and dissemination of digital materials created by the institution community members, including long-term preservation, access control, and distribution [7]; or the term current research information systems (CRISs)--a family of information systems used for storage and management of data about research conducted at an institution [8]. Their development can be based on a hosted solution [9] or custom implementations. Some insights on a qualitative comparison of IRs and CRISs can be found in [10]. In the cultural heritage (CH) field, digital repositories form the basis for implementing digital galleries, libraries, archives and museums, and archaeological datasets [11; 12; 13]. In addition to the possibility of cataloguing and disseminating digital versions of artefacts collected, these software systems offer specialized interfaces supporting multimedia [14]. With their help, browsing through scans of documents, archival audio/video recordings, 360 photos, or 3D models can take place not only on websites [15] but also in artificial or augmented reality. They may appear in the form of platforms running in the cloud or as software packages. Among them quite an important role is being played by collection management systems (CMSs)--software systems used to manage the whole lifecycle of preserved physical and digital materials, coordinate the undergoing tasks, control the responsibilities and access policies, etc. An example is ArchivesSpace, ([[https://archivespace.org](https://archivespace.org)]([https://archivespace.org](https://archivespace.org))). Quite close to discussed are content management systems (CMSs). They share the same abbreviation and several functions: support in describing the collected artefacts, usage monitoring, and access management. The examples of open source platforms of that sort are Mukurtu CMS ([[https://mukurtu.org](https://mukurtu.org)]([https://mukurtu.org](https://mukurtu.org))), Omega S ([[https://omega.org/s/](https://omega.org/s/)]([https://omega.org/s/](https://omega.org/s/))), and Collective Access ([[https://collectiveaccess.org](https://collectiveaccess.org)]([https://collectiveaccess.org](https://collectiveaccess.org))). The last in this list has two main components: Providence (engine) and Pawtucket2 (front end). It could be listed in Table 1, but it was not because of its narrowed application domain. For the same reason, all the platforms mentioned so far differ from the content management systems used to build web portals for publishing user content, such as Joomla ([[https://www.joomla.org](https://www.joomla.org)]([https://www.joomla.org](https://www.joomla.org))), Drupal ([[https://www.drupal.org](https://www.drupal.org)]([https://www.drupal.org](https://www.drupal.org))) and others. Another acronym that is often associated with DR is DRMS. DRMS stands for digital resource management system--a system or platform, most often aimed at managing and delivering various media assets to other systems.