![]() ![]() The associated set of files is the same between different metadata versions of the same record. Metadata version: Only metadata descriptions differ between metadata versions. Bear in mind though, that old metadata versions are still as public information as everything else in the current most recent version. The old metadata is simply being archived so that it may be accessed or restored later. It does not affect your current dataset’s identifiers, validity, or ability to access it or refer to it elsewhere. Identifiers are not generated by Metax: User has to provide any identifiers.Īs an end user who is editing the descriptions of their datasets, you generally shouldn’t care that new metadata versions are being created. ![]() Published datasets may not have all of the required metadata to qualify as Fairdata-dataset. Store legacy datasets that are published elsewhere. Other data catalogs where End Users can directly store dataset metadata: Store datasets which have data stored elsewhere than in the IDA Fairdata service. Store datasets which have files stored in the IDA Fairdata service. The official Fairdata data catalogs with end user write access are: The data catalog JSON schema file can be found here. The data catalog data model visualization can be found here. While reading datasets from all catalogs is possible by anybody (save for some data which might be considered as sensitive, such as personal information), adding datasets to catalogs can be restricted: Others allow adding only by known services, but some also by end users.ĭata catalogs can be browsed by using the API /rest/datacatalogs. Fairdata user provided datasets), slightly different schemas (IDA and ATT catalogs for example), and datasets in some catalogs are automatically versioned. Data catalogs house datasets with different origins (harvested vs. Harvested datasets are an exception: Harvested datasets will use the identifier in the original source as the preferred identifier.Įvery dataset belongs in a Data Catalog. When creating datasets in Metax, preferred identifiers are always automatically generated by Metax. When referring to a dataset in publications, tweets, or where ever in the outside world, preferred identifier is the identifier to use. Preferred identifier is the “public” identifier of a dataset. The internal identifier field always resides on the root level of the object retrieved from Metax API. Usually when identifier is mentioned in the documentation, by default it refers to the internal Metax identifier of an object. Catalog records can be considered the “technical” name of a dataset inside Metax. At the top level there are Data Catalogs, and Data Catalogs contain Catalog Records. The results returned from the API GET /rest/datasets/ are also sometimes called “catalog records”, or “records”. Retrieve minimal valid dataset template.About ResearchAgent, Organization, and Person.Using an existing dataset as a template.If-Modified-Since header in dataset API. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |