This interface allows users to login to MediaBeacon using either a local account (that is, an account managed by the MediaBeacon system), or authenticate against an Identity Provider (IDP) connected to MediaBeacon.
In some cases, users may bypass this interface when their organization uses a single sign on (SSO) or similar user authentication solution.
When local accounts are in use, the following links may be available:
- Forgot Password: Allows the user to send an email requesting password assistance to system administrators.
- Create Account: Allows users to enter a pre-generated code to create a local account.
Once logged in, the user will be redirected to the MediaBeacon Web UI.
MediaBeacon's Web UI allows users to view and interact with interface elements and data in the workspace. It can contain different arrangements of interface elements called components.
Users may have access to one or more workspaces, depending on what components are required for a given set of tasks.
For more on workspaces, see the [Workspace Basics] section.
In the Web UI, the term component refers to a set of interface elements that interact with the UI as a whole. For example, the Quick Search component allows the user to search for assets in MediaBeacon by entering a string of text to conduct a search.
Components may be placed in different areas of the workspace,.
There is a wide range of components available and many have administrator configurable options that change their functionality depending upon user needs. Note: In previous versions of MediaBeacon, components were referred to as widgets.
Components are often used together, so this guide arranges sets of functionalities together in the [Library Services] section.
For a comprehensive guide to the full options of each component, please see the [User Components Reference] section.
Files that are stored in MediaBeacon are referred to as assets. MediaBeacon can store any type of file and will create preview images for a wide range of file types.
Every asset has a number called the Asset ID (also referred to as the Record ID). This is an automatically assigned and non-editable value, unique to a specific asset in a specific MediaBeacon system.
If an asset is downloaded and uploaded to MediaBeacon, where another asset holds that number, a new Asset ID will be assigned to the newer upload. This is common if an asset is downloaded and then re-uploaded to the same MediaBeacon instance.
For more information on interacting with assets, see [Browse and View Assets] in the [Library Services] section.
User accounts are assigned to one or more access control lists, or ACLs.
Depending on the privileges granted by a given ACL, the user is allowed to use various functionalities involving assets, such as: uploading, reading and writing metadata, searching, or downloading. ACLs also grant access to specific workspaces, and to access specific sets of assets.
For example, in one ACL, a user might have the ability to download assets, and in another, they might be restricted from doing so.
Normal Contextual Menu
Contextual Menu with download restriction
For more information about interacting with ACLs, see the [Workspace Basics] section.
Metadata (data about data) is stored in MediaBeacon using the XMP format, which is written into the assets themselves. This allows the metadata to stay attached to the asset anywhere it goes so the metadata is readable to a wide variety of other applications.
The most common way to display metadata in MediaBeacon is by using the metaform, which collects several metadata fields together into one interface element.
Many metadata fields are based on industry standards, but it is quite likely that your organization will have unique fields and metaforms in which to display them.
For more information about interacting with metadata, see [Metadata] in the [Library Services] section.