Dismarc stick
From DISMARC Help
| Line 7: | Line 7: | ||
|} | |} | ||
| - | The partners can install these components from the stick to the local system (or just use them on the stick). | + | The partners can install these components from the stick to the local system (or just use them on the stick). Partners may upload their data to this local repository. |
| - | After setting up a local DISMARC node the partner can run periodically an automated data upload routine from the local cataloguing system to the local Metadata Manager Manager (via time-based scheduling services like cron on *nix and Schedule Tasks on Windows). The central DISMARC | + | After setting up a local DISMARC node the partner can run periodically an automated data upload routine from the local cataloguing system to the local Metadata Manager Manager (via time-based scheduling services like cron on *nix and Schedule Tasks on Windows). |
| + | |||
| + | If they want to have this local data being harvested (included) to the central DISMARC portal platform they will need to allow web access to the local server that hosts their metadata. | ||
| + | The central DISMARC Harvester will then periodically check for new data in the local system and harvest these updates to the central DISMARC portal plattform. | ||
| + | |||
| + | Further advantages: | ||
Running a local Metadata Manager additionally provides the possibility to connect to any OAI repository worldwide, if the partner wishes to distribute the metadata to other portals than DISMARC. Vice versa the local metadata manager might also be used to collect metadata information form other local sub-repositories before providing them all in one to DISMARC. This functionality supports the creation of national repositories spread over Europe that cumulate data and provide it to DISMARC (eg. a Swedish repository, German repository etc.) | Running a local Metadata Manager additionally provides the possibility to connect to any OAI repository worldwide, if the partner wishes to distribute the metadata to other portals than DISMARC. Vice versa the local metadata manager might also be used to collect metadata information form other local sub-repositories before providing them all in one to DISMARC. This functionality supports the creation of national repositories spread over Europe that cumulate data and provide it to DISMARC (eg. a Swedish repository, German repository etc.) | ||
Revision as of 16:09, 11 September 2008
DISMARC partners have the possibility to set up a local Metadata Manager (DISMARC system) at their site.
All the system components necessary to install such a local DISMARC Metadata Manager ship with the DISMARC stick.
 |
The partners can install these components from the stick to the local system (or just use them on the stick). Partners may upload their data to this local repository.
After setting up a local DISMARC node the partner can run periodically an automated data upload routine from the local cataloguing system to the local Metadata Manager Manager (via time-based scheduling services like cron on *nix and Schedule Tasks on Windows).
If they want to have this local data being harvested (included) to the central DISMARC portal platform they will need to allow web access to the local server that hosts their metadata. The central DISMARC Harvester will then periodically check for new data in the local system and harvest these updates to the central DISMARC portal plattform.
Further advantages:
Running a local Metadata Manager additionally provides the possibility to connect to any OAI repository worldwide, if the partner wishes to distribute the metadata to other portals than DISMARC. Vice versa the local metadata manager might also be used to collect metadata information form other local sub-repositories before providing them all in one to DISMARC. This functionality supports the creation of national repositories spread over Europe that cumulate data and provide it to DISMARC (eg. a Swedish repository, German repository etc.)
