Batch logging allows log page data to be set against multiple primary assets (media, audio, image) with a single Save action. 
NOTE: In this mode, it is not possible to mark in/out/bookmark values, and configured handles will be ignored.

Configuration

1. Add an entry to the child view selection that includes the setting media=”true” e.g., 
   <view name="ConceptInContextLoggingView" display="Batch Concept in Context" media=”true” numberOfColumns="2" />  
2. Optionally remove the use of parent media view, it is not necessary to use this view in most cases. This will reduce the number of pop-ups appearing. To remove the media view set the view name in viewSelections to an empty string, see blue below.
   • Sports Logging requires the Parent media view GameSelectionMediaView so it should not be removed even when you are batch logging on the media.
3. Optionally set <add key="UseFirstAsSourceOfTruth" value="true" /> in the web.config file to remove the need for and ability to select the asset to use as Source of Truth for parent metadata; the first loaded asset will be always used. This will reduce the number of pop-ups appearing e.g.: 
   
   <viewSelections display=""> 
   <view name="" display=""> 
   <subClipViewSelections> 
   <view name="ConceptInContextLoggingView" display="Batch Concept in Context" numberOfColumns="2" media="true"/> 
   </subClipViewSelections> 
   </view> 
   </viewSelections> 
   ... 
   <add key="UseFirstAsSourceOfTruth" value="true"/> 
   
    

Use

1. Select multiple primary assets from the Browse page (or from a Folder or a Collection containing primary assets) and click Start Logging.
   1. Avoid selecting clipmarks for now - any changes made here will affect their parent media/audio.
2. The Logging page will appear, displaying multiple items in the Sidebar.
3. If the parent media view was set a Media Metadata dialog may open - this will apply to the highlighted asset only. Close it.
4. Select the view that corresponds to the media="true" setting. This will have a media icon next to it rather than a clipmark icon.
5. Open the sidebar and select the assets you wish to enter to batch for logging. Hover over a thumbnail to see the name and the checkbox on the right, then select Done or click outside the sidebar. Further logging will apply only to the assets selected to batch.
6. Note that above the video player you now have a Batch Logging badge displayed. The Save button will now display Save Batch. 
   These act as a reminder that any action you take will apply to all assets in the selected batch.
7. If there is a parent media view in use, you will be prompted for Media Metadata. Set these, save, and close the pop-up.
   1. For Sports as on a single asset, you have to provide the 6 required metadata items so that the logging page can be set up for an appropriate Sport and Game's rosters and actions.
8. Start setting values on the Logging page. These values will be saved on all assets selected in the Batch.
9. When complete, click Save Batch to save your settings. Batch mode will exit.

To exit batch mode before making a log:

1. Open the sidebar by clicking on it.
2. Select Edit Batch.
3. Deselect assets individually until you have only one left OR deselect all assets using the checkbox above the first item.
4. Click Done.
   1. Only a single item in the list will be highlighted.
   2. The Batch Logging badge will disappear.
   3. The Save button will revert back to Save.
   4. You will be logging metadata only to the media selected and displayed in the player.

The most common problems include:

• The higher hierarchy metadata was set up , but there are no values for child metadata in the hierarchy 
  Usually, this means that in the data ingested via ETL there were no child values for that value of the parent (so no error but wrong expectation)
  • Check in the CSV file for a value that has children in the hierarchy and select it as a value for the parent, if you now see the expected children all should be working. 
• There are no values presented for any of the metadata in the hierarchy
  • Check MDC log files for the ETL ingest errors and correct these 
    The log file is located at C:\ProgramData\IPV\Metadata CentralService\Logs\Metadata Central.log on the MDC machine.
  • Check MDC log files for errors connected to bad requests and report to IPV.
  • Check Curator Server logs for errors received from MDC Teragator when GetOptions is requested.
    • If you misconfigured the Teragator endpoint entries in the Teragator config file or the deployment script there will be nothing in the Metadata Central log files, but Curator Server log files will report this or a similar error: 
      Failing to do that will result in a lack of metadata options in Curator Client applications and in Curator Server Logs, an error similar to this: 
      INFO OptionsProvider.Mdc.Slrql.MdcSlrqlQuery - [HttpProvider, MakeRestTransaction] - Received response code BadRequest from REST POST query. 
      ERROR Curator Server - Curator Server - [MetadataRepository, GetMetadataNameOptions] - One or more errors occurred.

The process to add or update the values served to supply hierarchical metadata consists of three steps:

1. Prepare a CSV document describing the terms and their hierarchy in the format, as shown below. Preparation and required format of the CSV files. For each top category (Topics and Countries by default), one CSV file will contain a new complete set of values to be stored and returned to Curator applications.
2. Use theIpvSkosGenerator provided as a zip file to generate the SKOS XML format.
3. Place the created SKOS XML file in the MDC Teragator Watchfolder (see Pre-requisites) to ingest the metadata values. Ensure the file is named exactly as referred to in the ETLSources.config, in the prerequisites example these would be skosTopics.xml or skosCountries.xml .

Detailed steps 

Extract the IpvSkosGenerator [version].zip. The top-level has a couple of example batch files: input includes example CSV files and Output includes example SKOS XML files. Items in the System subfolder should not be modified as this subfolder contains executable items and the necessary libraries.

Once the CSV document is ready, it is easiest to make your own batch (.bat) files (content here assumes the batch is present in the top directory of IpvSkosGenerator) referencing your input CSV and name for the output XML and the report file:

System\IpvSkosGenerator.exe --input "Input\NewTopics_update_1 _20010101.csv" --create
 "Output\NewTopics_update_1 _20010101.xml" --report "Output\NewTopics_update_1 _20010101.txt"

After executing the batch file, copy the resulting SKOS XML file (in this example: Output\NewTopics_update_1 _20010101.xml) to the Watchfolder created in the prerequisites, renaming it to match the relevant file referred to in the ETLSources.config file, in the prerequisites example above skosTopics.xml or skosCountries.xml.

Confirm that the ETL has ingested the update in the Teragator.log file (found in C:\ProgramData\IPV\Metadata Central Service\Logs path on the MDC Teragator server). When the database has successfully updated with the new set of values, this will be indicated by a "Database updated" statement similar to the following:

INFO TeragatorFramework.Api.ApiImplementation - ETL Ingest: timestamp=31/03/2022 10:23:17:
 status=SuccessStageComplete: OntologyWriter.Process(): Database updated

Preparation and required format of the CSV files:

1. The first row contains headers - place the column labels exactly as indicated: 
   document created date, document label, preferred label of concept, preferred label of narrower concept, alternate label of concept, definition of concept.
2. Below that, empty lines are allowed in order to make it easier to separate parts of the file. 
3. You can use only a certain list 
4. The first data line has the values for "document created date" and "document label". These must be set and apply to the entire document. The document created date is in the format DD/MM/YYYY. Document label has to be unique to a document to be updated. In the example below the unique document label is "Keyword Lists". If you require additional document it will need to have a different document label e.g. "Campaigns".
5. Each item to be ingested as a value for metadata must be added in the "preferred label of concept" column. The "alternate label of concept" and "definition of concept" are optional additional descriptions.
6. To create a hierarchy, create pairs of "preferred label of concept" and "preferred label of narrower concept".
   • You must declare the top-level hierarchy items as Topics and Countriesto use with the resource deployment Context MDC 2.2-SKOS Resource Metadata View.sql with only minor modifications commented within.
     • If you require different top-level categories, you will have to further modify the resource deployment script as described in the section above: Configuration steps to deploy Logger
   • Within Topics, declare the categories you require (in the below example Business and Leisure) as "preferred label of narrower concept".
   • Declare each of these categories as "preferred label of concept".
   • Declare for each of these the list of the "preferred label of narrower concept".
   • Finally, declare the lowest level as "preferred label of concept"  in their own right - these will not have any narrower concept declared.
   • You can continue declaring the hierarchy deeper in, but remember that to use these you will need to declare the metadata for these and create and assign the resources appropriately, which requires more complicated intervention to the scripts.
   • Remember to save the file as a CSV.