Metadata views
A view is a collection of fields. A field corresponds to one piece of data that you enter as part of a metadata object. For example, title, description, author, date created, and rights are all possible fields. Different views enable users to see and modify different fields when looking at metadata.
Brightspace includes six base metadata views that implement widely used metadata standards:
- Dublin Core (http://dublincore.org/documents/) - This view categorizes metadata using 15 different elements: contributor, coverage, creator, date, description, format, identifier, language, publisher, relation, rights, source, subject, title, and type.
- GEM - This view categorizes metadata using 9 different elements: general, life cycle, meta-metadata, technical, educational, rights, relation, annotation, and classification.
- IEEE LOM - This view categorizes metadata using the 15 Dublin Core elements, plus 7 additional elements: audience, cataloging, duration, essential resources, pedagogy, quality, and standard.
- Normetic (http://www.normetic.org/ (French) or http://www.normetic.org/-English-.html (English)) - This view is a French version you can use to categorize metadata based on the IEEE LOM view.
- Object Publishing - This view categorizes metadata based on a simplified Dublin Core view using 3 different elements: title, description, and keywords.
- Object Publishing IEEE LOM - This view categorizes metadata based on a simplified IEEE LOM view using 3 different elements: title, description, and keywords.
Default system views refer to any of the views that ship with Brightspace by default.
Brightspace also includes two default system views that inherit from the IEEE LOM base view:
Create a metadata view
Creating a new metadata view may be necessary for any number of reasons. For example, you might require a view for a specific department to refine the general organization’s view, or a simplified view for users who do not require access to all of the metadata associated with your organization’s resources.
You can create new views based on any of the available views, including views you have previously created. When creating a new view, you can rename, reorganize, and hide fields, change field types, and set data restrictions; however, you cannot add additional fields or radically alter the structure of the base view.
Some of the fields in IEEE LOM and Dublin Core are cross-walked, meaning the values from those fields automatically synchronize between the two views. In fields that are not cross-walked, the values entered in a view from one family are not visible across families.
Keep this in mind when you determine what views to make available to users in your organization. Views within the same family provide different ways of looking at (or entering) the same metadata, but views in different families provide access to different metadata.
- From the Admin Tools menu, click Metadata Administration.
- On the Views page, click New View.
- Enter a View Name.
- From the Parent View drop-down list, select the parent view that contains the structure that you want your view to inherit.
- Do one of the following:
- If you want your view to inherit its settings from its parent, select Inherit Properties from Parent View.
- If you want your view to copy properties from an existing view, select Copy Properties from an Existing View.
- Click Save.
- On the Edit View page, using the provided tabs, further customize your General, Restrictions, and Layout options.
- Click Save.
Import a metadata view
You can add a metadata view by importing an XML file into Brightspace.
Brightspace treats any view that you import as a customized view and maintains the language terms defined in the org unit that the view comes from. For example, if a French org defines a view with French terms and exports the view, then when you import the view in another org unit, users see the French terms even if they are using English.
- From the Admin Tools menu, click Metadata Administration.
- On the Views page, from the More Actions button, click Import View.
- On the Import View page, enter a View Name.
- To select the view that you want to import, click Browse. Locate your file and click Open.
- Click Import.
Export a metadata view
You can export a metadata view as an XML file. When you export a metadata view, it retains the language terms that you have in your org unit. For example, your French org defines a view with French terms and exports the view, then when other users import the view in another org unit, they see the French terms even if they are using English.
- From the Admin Tools menu, click Metadata Administration.
- On the Views page, from the More Actions button, click Export View.
- From the Export View drop-down list, select the view you want to export.
- Click Export.