# Adding Representation Information For example the archive may add Representation Information which was not required because it has been common knowledge previously, for example the definition of a specific variant of FITS or an XML schema which is no longer available at its normal URI (schemaLocation). If software which is commonly available becomes, or threatens to become, unavailable or unusable in some way, then the Representation Information to be added could be a software installation kit and/or a software emulator or Virtual Machine, perhaps with a machine emulator such as [QEMU](https://www.qemu.org/), or a [Docker ](https://www.docker.com/)container. Each of these may require its own Representation Information, for example a Docker container needs underlying support such as an operating system. Details are provided, following OAIS, in: * [Structural Representation Information](/labdrive/data-curation-and-preservation-1/preservation-activities/adding-representation-information/structural-representation-information.md) * [Semantic Representation Information](/labdrive/data-curation-and-preservation-1/preservation-activities/adding-representation-information/semantic-representation-information.md) * [Other Representation Information](/labdrive/data-curation-and-preservation-1/preservation-activities/adding-representation-information/other-representation-information.md)which includes * [Software as part of the RIN](/labdrive/data-curation-and-preservation-1/preservation-activities/adding-representation-information/other-representation-information/software-as-part-of-the-rin.md) - including a description of how to preserve software, including Jupyter Notebooks, Virtual Machines and Containers. If the additional Representation Information is essentially a replacement for the existing Representation Information, for example replacing a text file which is a placeholder saying "Need to add more details here", or perhaps a formal data description which has an improved version, then the [File Versioning](/labdrive/get-started/file-versioning-and-recovery.md) may be used so that existing pointers to the original file will automatically pick up the new version. If, on the other hand, it is important to keep other versions of the Representation Information available simultaneously, then the versioning technique of referring to a folder which contains all the different versions of a file (the Representation Information) would be appropriate. ### Tools for adding Representation Information Representation Information may be added as "metadata" elements to the OAIS Archival Information Model Schema associated with the Data Object in one of a number of ways see [Configure metadata](/labdrive/configuration/metadata.md): * using the GUI * using the API via the command line or script as CURL commands, or via a programming language such as PYTHON or JAVA. The metadata may be a link to another Data Object, which itself may have one or more "metadata" elements in its OAIS Archival Information Model Schema, or it may be a text description. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.libnova.com/labdrive/data-curation-and-preservation-1/preservation-activities/adding-representation-information.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.