## 3 Materials and Methods
### Requirements Analysis  
Below are the general and specific requirements for the AZON platform's functions (bolded parts are directly related to multimedia processing).  
* Depositing--upon deposit, quality control of data records should be concerned. Thus, the platform should support the editing and review of data records by different users. Moreover, depositing should be possible through GUI and API, in the context of the depositor or his representative. Large data records that cannot be loaded into the repository with the HTTP protocol should also be supported.
* Publishing--published data records should appear on a website in collective and individual views, in both human and machine-readable form. The rendering should be consistent for all supported types of data records while ensuring their high availability. The data centre should activate batch processing of data (including, among others, standardization, annotation, generation of voice transcription, indexing for search purposes, linking, and determination of keywords). Records' use should be monitored, and their correction and curation should be possible.
* Searching and browsing--published data records should be searchable in various ways (simple, advanced, faceted, by browsing, and with filtering). This requirement involves indexing their attributes and supporting the full-text search. The parameterization of search queries should be supported by utilizing dictionaries. Dictionary management (creating, adding, deleting, modifying terms) and accessing them (e.g., finding related terms in advanced search) should be possible through GUI and API.
* Securing--three pillars of security must be provided by the infrastructure: authentication, authorization, and monitoring. Moreover, the functions offered should correspond to the adopted security policies and formal procedures (including audits, issues handling, etc.).
* Maintaining--the system should ensure secure preservation of deposited resources and their long-term maintenance. The former function includes checking for consistency and physical integrity, backing up, storing several copies in different locations, etc. The latter involves checking for up-to-date links and migrations triggered by introducing new data types or upgrades of system hardware and software.  
The original list of requirements was much longer and detailed. It also included the set of technical requirements for audio/video processing that can be shortened as follows:  
* Audio/video handling--uploading large video or audio should be supported, together with the assignment of unique IDs and publicly accessible links (so audio/video players can use that).
* Transcripts/subtitles handling--uploading multiple transcription text files, subtitles and associate them with the corresponding video should be possible.
* Streaming--video streaming and rendering with subtitling in the player on zasoby-nauki.com is expected.
* Video processing--adapting the stream's quality to the quality of the connection (or choosing the quality from offered options in the player) is required.
* Video type supporting--the solution must assure support for HLS (and/or MPEG-DASH).