EPrints Documentation - User contributions [en-gb]

Files/OpenAIRE Compliance Plug-in

2011-03-22T09:37:52Z

Rob.ingram@nottingham.ac.uk: moved Files/OpenAIRE Compliance to Files/OpenAIRE Compliance Plug-in: Match auto-generated wiki page from files.eprints.org

This EPrints extension is designed to help the administrators of repositories that contain outputs from EU FP7 funded projects to achieve compliance with the OpenAIRE Guidelines version 1.1 (http://www.openaire.eu/index.php?option=com_content&view=article&id=207).

In summary, these guidelines state that the outputs from FP7 projects must be made avaiable for harvesting via OAI-PMH using a defined set specification. In addition these outputs should meet certain standards in their metadata as defined in the guidelines document.

==What this add-on does and doesn't do==

===This add-on will===

* Add new metadata fields for EU FP7 specific elements
* Map the default EPrints data types to their DRIVER equivalents (see http://www.driver-support.eu/documents/DRIVER_Guidelines_v2_Final_2008-11-13.pdf, page 69)
* Create a new custom set within the OAI-PMH output of the repository called EC_fundedresources and containing all resources that are flagged as being outputs of FP7 projects
* Add required metadata to the OAI-PMH output
* Check if any files have an embargo date specified (and are restricted access) and alter the rights field in OAI-PMH output to reflect this

===This add-on will not===

* Check whether items flagged as outputs of FP7 projects have a Project ID specified in the correct format before including them in the EC_fundedresources set
* Check whether items flagged as outputs of FP7 projects have full text available before including them in the EC_fundedresources set
* Check whether items flagged as outputs of FP7 projects have all required metadata set (e.g. DC.rights)

This is due to the fact that EPrints custom sets can only currently filter on a single metadata value (in this case we're using the flag that states that the resource is form an FP7 funded project).

==Installation (EPrints 3.1+)==

Download the latest tarball to your local repository directory (eg. /opt/eprints3/archives/ARCHIVEID/)

Extract files:

tar xzvf eprints-openaire.xx.tgz

===Update database===

Add the new metadata fields to your database:

cd [eprints_root]/bin
./epadmin update_database_structure ARCHIVEID --verbose

==Getting started==

To activate the OpenAIRE compliance features you will need to make some changes to your repository setup.

In file cfg/cfg.d/eprint_fields_automatic.pl add the following lines:

# Map Eprints type to DRIVER type
my %type_map = (
"article" => "info:eu-repo/semantics/article",
"book_section" => "info:eu-repo/semantics/bookPart",
"monograph" => "info:eu-repo/semantics/book",
"conference_item" => "info:eu-repo/semantics/conferenceObject",
"book" => "info:eu-repo/semantics/book",
"patent" => "info:eu-repo/semantics/patent"
);

my $mapped_type = (exists $type_map{$type}) ? $type_map{$type} : "info:eu-repo/semantics/other";
$eprint->set_value("fp7_type", $mapped_type)

In file cfg/workflows/eprint/default.xml add the following lines before the closing </workflow> tag:

<stage name="fp7">
<component type="Field::Multi">
<title>Details for FP7 project outputs</title>
<field ref="fp7_project"/>
<field ref="fp7_project_id"/>
<field ref="access_rights"/>
</component>
</stage>

And add the following line to the <flow> element (near the start of the file) to place the new FP7 stage where you feelit will be most appropriate for your workflow:

<stage ref="fp7"/>

e.g.:

<flow>
<stage ref="type"/>
<stage ref="files"/>
<stage ref="core"/>
<stage ref="subjects"/>
<stage ref="fp7"/>
</flow>

Restart apache to ensure that all the changes are applied.

Files/OpenAIRE Compliance

2011-03-22T09:37:52Z

Rob.ingram@nottingham.ac.uk: moved Files/OpenAIRE Compliance to Files/OpenAIRE Compliance Plug-in: Match auto-generated wiki page from files.eprints.org

#REDIRECT [[Files/OpenAIRE Compliance Plug-in]]

Files/OpenAIRE Compliance Plug-in

2011-03-22T09:03:19Z

Rob.ingram@nottingham.ac.uk:

Files/OpenAIRE Compliance Plug-in

2011-03-17T16:16:52Z

Rob.ingram@nottingham.ac.uk:

IN PROGRESS

This EPrints extension is designed to help the administrators of repositories that contain outputs from EU FP7 funded projects to achieve compliance with the OpenAIRE Guidelines version 1.1 (http://www.openaire.eu/index.php?option=com_content&view=article&id=207).

In summary, these guidelines state that the outputs from FP7 projects must be made avaiable for harvesting via OAI-PMH using a defined set specification. In addition these outputs should meet certain standards in their metadata as defined in the guidelines document.

==What this add-on does and doesn't do==

===This add-on will===

* Add new metadata fields for EU FP7 specific elements
* Map the default EPrints data types to their DRIVER equivalents (see http://www.driver-support.eu/documents/DRIVER_Guidelines_v2_Final_2008-11-13.pdf, page 69)
* Create a new custom set within the OAI-PMH output of the repository called EC_fundedresources and containing all resources that are flagged as being outputs of FP7 projects
* Add required metadata to the OAI-PMH output
* Check if any files have an embargo date specified (and are restricted access) and alter the rights field in OAI-PMH output to reflect this

===This add-on will not===

* Check whether items flagged as outputs of FP7 projects have a Project ID specified in the correct format before including them in the EC_fundedresources set
* Check whether items flagged as outputs of FP7 projects have full text available before including them in the EC_fundedresources set
* Check whether items flagged as outputs of FP7 projects have all required metadata set (e.g. DC.rights)

This is due to the fact that EPrints custom sets can only currently filter on a single metadata value (in this case we're using the flag that states that the resource is form an FP7 funded project).

==Installation (EPrints 3.1+)==

Download the latest tarball to your local repository directory (eg. /opt/eprints3/archives/ARCHIVEID/)

Extract files:

tar xzvf eprints-openaire.xx.tgz

===Update database===

Add the new metadata fields to your database:

cd [eprints_root]/bin
./epadmin update_database_structure ARCHIVEID --verbose

==Getting started==

To activate the OpenAIRE compliance features you will need to make some changes to your repository setup.

In file cfg/cfg.d/eprint_fields_automatic.pl add the following lines:

# Map Eprints type to DRIVER type
my %type_map = (
"article" => "info:eu-repo/semantics/article",
"book_section" => "info:eu-repo/semantics/bookPart",
"monograph" => "info:eu-repo/semantics/book",
"conference_item" => "info:eu-repo/semantics/conferenceObject",
"book" => "info:eu-repo/semantics/book",
"patent" => "info:eu-repo/semantics/patent"
);

my $mapped_type = (exists $type_map{$type}) ? $type_map{$type} : "info:eu-repo/semantics/other";
$eprint->set_value("fp7_type", $mapped_type)

In file cfg/workflows/eprint/default.xml add the following lines before the closing </workflow> tag:

<stage name="fp7">
<component type="Field::Multi">
<title>Details for FP7 project outputs</title>
<field ref="fp7_project"/>
<field ref="fp7_project_id"/>
<field ref="access_rights"/>
</component>
</stage>

And add the following line to the <flow> element (near the start of the file) to place the new FP7 stage where you feelit will be most appropriate for your workflow:

<stage ref="fp7"/>

e.g.:

<flow>
<stage ref="type"/>
<stage ref="files"/>
<stage ref="core"/>
<stage ref="subjects"/>
<stage ref="fp7"/>
</flow>

Restart apache to ensure that all the changes are applied.

Files/OpenAIRE Compliance Plug-in

2011-03-17T16:16:08Z

Rob.ingram@nottingham.ac.uk:

Files/OpenAIRE Compliance Plug-in

2011-03-17T16:15:09Z

Rob.ingram@nottingham.ac.uk:

Files/OpenAIRE Compliance Plug-in

2011-03-17T16:07:15Z

Rob.ingram@nottingham.ac.uk:

Files/OpenAIRE Compliance Plug-in

2011-03-17T15:52:12Z

Rob.ingram@nottingham.ac.uk:

IN PROGRESS

An EPrints extension to help achieve compliance with the OpenAIRE guidelined for repositories containing outputs from European Commission FP7 projects.

==Installation (EPrints 3.1+)==

Download the latest tarball to your local repository directory (eg. /opt/eprints3/archives/ARCHIVEID/)

Extract files:

tar xzvf xxx_xx.tgz

Files/OpenAIRE

2011-03-17T15:48:52Z

Rob.ingram@nottingham.ac.uk: moved Files/OpenAIRE to Files/OpenAIRE Compliance

#REDIRECT [[Files/OpenAIRE Compliance]]

Files/OpenAIRE Compliance Plug-in

2011-03-17T15:48:52Z

Rob.ingram@nottingham.ac.uk: moved Files/OpenAIRE to Files/OpenAIRE Compliance

__END__

Files/OpenAIRE Compliance Plug-in

2011-03-17T15:44:58Z

Rob.ingram@nottingham.ac.uk: Created page with '__END__'

__END__