Dismarc stick

From DISMARC Help

(Difference between revisions)
Jump to: navigation, search
Current revision (10:52, 12 September 2008) (edit) (undo)
 
(18 intermediate revisions not shown.)
Line 1: Line 1:
-
DISMARC partners have the possibility to set up a '''local Metadata Manager''' (DISMARC system) at their site.
+
The installed DISMARC system ships with the '''DISMARC stick.'''
-
 
+
-
All the system components necessary to install the local DISMARC Metadata Manager ship with the DISMARC stick.
+
{|
{|
Line 7: Line 5:
|}
|}
-
The partners can install these components from the stick to the local system (or just use them on the stick). The local server that hosts the local metadata needs to allow Web Access so that the central DISMARC Harvester can collect the data online from there.
+
The partners can run the installed system on the stick or any other writeable medium using the <u>VMWare Player</u>. The VMWare Player has to be installed on the local computer. (This piece of software is located on the stick or can be downloaded from www.vmware.com.)
 +
 
 +
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 [[Admin Area#The data import|harvested by 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 <u>connect to any OAI repository worldwidea</u>, 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 <u>supports the creation of national repositories</u> spread over Europe that cumulate data and provide it to DISMARC (eg. a Swedish repository, German repository etc.)
 +
 
 +
 
 +
'''Find below two screencasts that describe how to use the DISMARC stick:'''
 +
 
 +
<flash>file=screencast_01.swf|width=820|height=600</flash>
 +
 
 +
<flash>file=screencast_02.swf|width=820|height=600</flash>
 +
 
 +
 
-
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 MetaDataManager will then periodically check for new data in the local system and harvest these updates to the central DISMARC portal plattform.
 
-
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.)
+
[[Category: Dismarc portal]]

Current revision

The installed DISMARC system ships with the DISMARC stick.

DISMARC stick
DISMARC stick

The partners can run the installed system on the stick or any other writeable medium using the VMWare Player. The VMWare Player has to be installed on the local computer. (This piece of software is located on the stick or can be downloaded from www.vmware.com.)

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 by 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 worldwidea, 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.)


Find below two screencasts that describe how to use the DISMARC stick:

Personal tools