Voorbeelden van het gebruik van Each dataset in het Engels en hun vertalingen in het Nederlands
{-}
-
Colloquial
-
Official
-
Ecclesiastic
-
Medicine
-
Financial
-
Computer
-
Ecclesiastic
-
Official/political
-
Programming
Each dataset follows a schema.
Right now, we process each dataset by hand.
Each dataset is made up of metadata and resources.
All distributions of each dataset are checked.
Typically˜4000 spikes should be selected for each dataset.
Then for each dataset there is a Monitoring link.
According to the DCAT-AP specification, each dataset must have an AccessURL;
Each dataset is represented by a rectangle called a"catalog card.
There will be time at later stages to check in detail whether each dataset is suitable.
On the catalog page of your domain, each dataset is represented by a single catalog card.
along with the current amount of API calls for each dataset.
According to the DCAT-AP specification, each dataset must have an AccessURL;
along with the current amount of reuses for each dataset.
Each dataset is defined by a dictionary of metadata,
along with the current amount of downloads for each dataset.
Although the metadata can be set individually for each dataset afterward, it is possible to configure the default location(s)
In the Opendatasoft platform, all processing operations are done in the Processing tab of the edition interface of each dataset.
edition permissions on a per dataset basis, on each dataset publishing interface.
In the Opendatasoft platform, the configuration of the available exports is done in the Export tab of the edition interface of each dataset.
it is not required to provide a schema file for each dataset in the index. csv.
In the Opendatasoft platform, the configuration of a dataset source is done in the Source tab of the edition interface of each dataset.
Enabling the reuse feature on your portal will display a new Reuses section at the bottom of the information tab on each dataset page.
description of each dataset.
downloads and citations for each public dataset.
It will then create an unpublished dataset for each remote dataset it finds.
They should be configured in the Information tab of the edition interface of a dataset, each type of metadata having their own specific tab.