Skip to content

Latest commit

 

History

History
62 lines (52 loc) · 2.69 KB

README.adoc

File metadata and controls

62 lines (52 loc) · 2.69 KB
Raw

Media Archive Admin project

An application providing a simple admin UI for the (union) media archive.

Description

This sub project contains an application that displays information about the current status of the union media archive and the archive components that contribute media files to it. For the total union archive and each archive component, there are some statistics such as the number of medias and songs currently available and the total size occupied on disk and playback duration. There are actions to trigger a new media scan or to cancel a currently running scan.

A separate dialog window can be opened allowing the management of persistent meta data files. Local media archives create such files to store the meta data of media files after it has been extracted. Thy are named by a checksum value calculated based on the content of the medium. If the currently selected archive component uses such files, they can be displayed and updated via this meta data files dialog. A use case for this is that once written meta data files are not deleted automatically, even if the associated medium is changed or no longer exists. This can be done manually via this dialog.

The OSGi bundle produced by this project can be deployed into an OSGi framework hosting the LineDJ platform. The archive admin UI is then available; communication with the media archive happens via the same channel as used by other platform applications.

Configuration

As usual, the configuration for the archive admin application is read from the configuration file of the LineDJ management application. It is placed in a section named media.validation and supports a limited number of settings:

<configuration>
  <media>
    <validation>
      <validationParallelism>4</validationParallelism>
      <uiUpdateChunkSize>16</uiUpdateChunkSize>
    </validation>
  </media>
</configuration>

The options available are explained in the table below:

Table 1. Configuration options for the archive admin application
Setting Description Default

validationParallelism

Defines the degree of parallelism in which validation of archive entries is performed. This corresponds to the number of elements that are processed in parallel.

4

uiUpdateChunkSize

Defines an update rate for the UI that displays validation results. Validation happens in background; the UI is updated when new results are available. With this property it can be specified that updates are not needed for every new result, but only when the given number of results is reached. If there are many validation errors, a larger chunk size can improve performance.

16