# Ontology metadata :::warning (Need update: imported from AgroPortal project management Wiki on 2022-11-17) ::: We have implemented significant changes (compare to the NCBO BioPortal) in terms of ontology metadata. This is explained in a publication in *Data Semantics Journal*: We have implemented a new metadata model to support better descriptions of ontologies and their relations with respect of the standards metadata vocabularies used in the semantic web community. We have reviewed the most standard and relevant vocabularies out-there to describe metadata for ontologies (such as: Dublin Core, VoID, Ontology Metadata Vocabulary, Data Catalog Vocabulary, etc.) cf. . We then grouped those properties into a unified and simplified model of 127 properties that includes the 45 properties originally offered by the NCBO BioPortal and describe all the new properties with standard vocabularies. We have now for instance a model to capture which kind of knowledge organization source the file uploaded to the portal is (e.g., thesaurus, ontology, taxonomy, terminology, etc.). This has resulted in three important new features for AgroPortal: * Once an ontology is uploaded, AgroPortal extracts automatically most of the ontology metadata if they are included in the original file or automatically populate some of them (e.g., metrics, endpoints, links, examples). Those values can manually be changed after by ontology developers if they want to provide another value. If they are actually found in the file, most of the 127 properties of the model will be automatically extracted out of 346 potentially relevant properties taken from 23 standard metadata vocabularies. The available parsed and selected metadata properties [are available](https://github.com/agroportal/documentation/tree/master/metadata). In addition, we have entirely redesigned AgroPortal’s ontology submission page to facilitate the edition of the metadata. Every time it is possible, the user interface facilitates the selection of the metadata values, while, in the backend those values are stored with standard URIs. For instance, the user interface will offer a pop-up menu to select the relevant license (e.g., CC, BSD, etc.) while the corresponding URI will be taken from RDFLicense dataset ([http://rdflicense.appspot.com](http://rdflicense.appspot.com/)). KOS types are taken from the KOS Types Vocabulary from the Dublin Core initiative. * AgroPortal ontology browse page offers now 3 additional ways to filter ontologies in the list (content, natural language, formality level) as well as 2 new options to sort this list. We believe these new features facilitate the process of selecting the relevant ontologies to use. E.g., * Our goal is to facilitate the comprehension of the agronomical ontology landscape by displaying diagrams and charts about all the ontologies on the portal (average metrics, most used tools, leading contributors & organization, etc.). We have released new AgroPortal page that will display metadata “by property” (as opposed as “by ontology”): * After an ontology is uploaded, while we often edit ourselves ontology descriptions, we ask the ontology developers to validate our edits and complete them. * We have develop a "Get my metadata back" feature that will enable someone to export the metadata of an ontology in any OWL syntax, to copy paste it in the original ontology file. This is still in beta, but works (see top right corner of the Summary page). We are currently working in generalizing this work on ontology metadata to develop an Application Profile and an ontology for metadata: . The version 1.2 of MOD has been published at MTSR 2017 conference: [http://www.lirmm.fr/\\\~jonquet/publications/documents/Article_MTSR-2017_MOD1.2.pdf](http://www.lirmm.fr/%5C\~jonquet/publications/documents/Article_MTSR-2017_MOD1.2.pdf) This is now discussed within the RDA VSSIG Ontology Metadata Task Group (join us on Slack: [https://vocabulary-services.slack.com](https://vocabulary-services.slack.com/)). --- **Documents** - [💁‍♂️ Acknowledgments](https://wiki.agroportal.eu/s/e6158eda-c109-4385-852c-51a42de9a412/doc/acknowledgments-15GdRXLQdm) - [📚Publications and references](https://wiki.agroportal.eu/s/e6158eda-c109-4385-852c-51a42de9a412/doc/publications-and-references-87tEoeoGKy) - [🗽Terms & Conditions](https://wiki.agroportal.eu/s/e6158eda-c109-4385-852c-51a42de9a412/doc/terms-conditions-naDsDo2Zxq) - [🧞‍♂️Metadata guidelines and recommendations](https://wiki.agroportal.eu/s/e6158eda-c109-4385-852c-51a42de9a412/doc/metadata-guidelines-and-recommendations-pOFbK9sIfp) - [📜 AgroPortal Release Notes](https://wiki.agroportal.eu/s/e6158eda-c109-4385-852c-51a42de9a412/doc/agroportal-release-notes-btKjZk5tU2) - [ 👩‍🚀 User Guide](https://wiki.agroportal.eu/s/e6158eda-c109-4385-852c-51a42de9a412/doc/user-guide-ZszoBwfjGF) - [📎 API Documentation](https://wiki.agroportal.eu/s/e6158eda-c109-4385-852c-51a42de9a412/doc/api-documentation-kMCurGKD97) - [🤖 Developer Documentation](https://wiki.agroportal.eu/s/e6158eda-c109-4385-852c-51a42de9a412/doc/developer-documentation-LhsrucqGTa) - [🗃External Documentation](https://wiki.agroportal.eu/s/e6158eda-c109-4385-852c-51a42de9a412/doc/external-documentation-vNPQCdArrr) - [AgroPortal infrastructure](https://wiki.agroportal.eu/s/e6158eda-c109-4385-852c-51a42de9a412/doc/agroportal-infrastructure-ietsAU4kPs)