General Open Access Topics
Main.General History
Hide minor edits - Show changes to output
Changed lines 12-13 from:
DRIVER, the Digital Repository Infrastructure Vision for European Research is proud to announce the software release D-NET v. 1.0. The first of its kind, this open source software offers a tool-box for deploying a customizable distributed system featuring tools for harvesting and aggregating heterogeneous data sources. A variety of end-user functionalities are applied over this integration, ranging from search, recommendation, collections, profiling to innovative tools for repository manager users. The official press release is available [[http://www.driver-repository.eu/DRIVER-News-Events/PR_D-NET_1_0.html | here]]. Please also see the [[DRIVER Infrastructure|Infrastructure and Services]] section of this wiki for further details.
to:
DRIVER, the Digital Repository Infrastructure Vision for European Research is proud to announce the software release D-NET v. 1.0. The first of its kind, this open source software offers a tool-box for deploying a customizable distributed system featuring tools for harvesting and aggregating heterogeneous data sources. A variety of end-user functionalities are applied over this integration, ranging from search, recommendation, collections, profiling to innovative tools for repository manager users. The official press release is available [[http://www.driver-repository.eu/DRIVER-News-Events/PR_D-NET_1_0.html | here]]. Please also see the [[DRIVER Infrastructure| DRIVER Infrastructure and Service Providers]] section of this wiki for further details.
Changed lines 24-25 from:
In response to requests from the repository community, and with input from UKCoRR members, %newwin%[[http://www.sherpa.ac.uk|SHERPA]] has compiled a skills set and description of the common repository roles/jobs needed to develop and manage a UK institutional repository. The document can be found on the SHERPA [[http://www.sherpa.ac.uk/news/Aug2007-01.htm|website]].
to:
In response to requests from the repository community, and with input from UKCoRR members, %newwin%[[http://www.sherpa.ac.uk|SHERPA]] has compiled a skills set and description of the common repository roles/jobs needed to develop and manage a UK institutional repository. The document can be found on the SHERPA [[http://www.sherpa.ac.uk/news/staffandskillssecondrevision.html|website]].
Changed lines 12-13 from:
DRIVER, the Digital Repository Infrastructure Vision for European Research is proud to announce the software release D-NET v. 1.0. The first of its kind, this open source software offers a tool-box for deploying a customizable distributed system featuring tools for harvesting and aggregating heterogeneous data sources. A variety of end-user functionalities are applied over this integration, ranging from search, recommendation, collections, profiling to innovative tools for repository manager users. The official press release is available [[http://www.driver-repository.eu/DRIVER-News-Events/PR_D-NET_1_0.html | here]]. Please also see the [[DRIVER Infrastructure|Infrastructure]] section of this wiki for further details.
to:
DRIVER, the Digital Repository Infrastructure Vision for European Research is proud to announce the software release D-NET v. 1.0. The first of its kind, this open source software offers a tool-box for deploying a customizable distributed system featuring tools for harvesting and aggregating heterogeneous data sources. A variety of end-user functionalities are applied over this integration, ranging from search, recommendation, collections, profiling to innovative tools for repository manager users. The official press release is available [[http://www.driver-repository.eu/DRIVER-News-Events/PR_D-NET_1_0.html | here]]. Please also see the [[DRIVER Infrastructure|Infrastructure and Services]] section of this wiki for further details.
Changed lines 14-16 from:
to:
!!Other Infrastructures and Services
(Here please add details of any other repository infrastructures or services)
(Here please add details of any other repository infrastructures or services)
Changed lines 9-10 from:
The DRIVER Guidelines were developed based on the DINI certification in Germany and DARE guidelines in the Netherlands with requirements specific to those networks removed. DRIVER partners involved in other repository networks, such as HAL in France and SHERPA in the UK, provided additional input to ensure that the DRIVER Guidelines are suitable for implementation by the entire European repository community. The DRIVER Guidelines are available from the %newwin%[[http://www.driver-support.eu/managers.html | Support website]]. A Wiki page has been set up for the [[DRIVERGuidelines|DRIVER Guidelines]] where you may contribute.
to:
The DRIVER Guidelines were developed based on the DINI certification in Germany and DARE guidelines in the Netherlands with requirements specific to those networks removed. DRIVER partners involved in other repository networks, such as HAL in France and SHERPA in the UK, provided additional input to ensure that the DRIVER Guidelines are suitable for implementation by the entire European repository community. The DRIVER Guidelines are available from the %newwin%[[http://www.driver-support.eu/managers.html | Support website]]. A Wiki has been set up for the [[http://www.surffoundation.nl/wiki/display/DRIVERguidelines/Home |DRIVER Guidelines]] where you may contribute.
Changed lines 44-51 from:
In trying to populate a repository it can be more successful to concentrate on encouraging researchers to deposit their recent publications rather than asking them to deposit all their publications to date.
to:
In trying to populate a repository it can be more successful to concentrate on encouraging researchers to deposit their recent publications rather than asking them to deposit all their publications to date. Many researchers will have difficulty finding copies of their older publications and this may cause them to give up searching even for the more recent publications.
Try to find researchers who are willing promote the repository to their colleagues, the message is often stronger when it comes from a researcher rather than a repository manager or librarian.
Highlight the successes of the repository. Use download or other statistics to show how often publications in the repository are accessed. Information like this can make good articles for inclusion in your institution's newsletters etc.
Try to find researchers who are willing promote the repository to their colleagues, the message is often stronger when it comes from a researcher rather than a repository manager or librarian.
Highlight the successes of the repository. Use download or other statistics to show how often publications in the repository are accessed. Information like this can make good articles for inclusion in your institution's newsletters etc.
Changed lines 9-10 from:
The DRIVER Guidelines were developed based on the DINI certification in Germany and DARE guidelines in the Netherlands with requirements specific to those networks removed. DRIVER partners involved in other repository networks, such as HAL in France and SHERPA in the UK, provided additional input to ensure that the DRIVER Guidelines are suitable for implementation by the entire European repository community. The DRIVER Guidelines are available from the %newwin%[[http://www.driver-support.eu/documents/DRIVER_guidelines_1%200.pdf | Support website]]. A Wiki page has been set up for the [[DRIVERGuidelines|DRIVER Guidelines]] where you may contribute.
to:
The DRIVER Guidelines were developed based on the DINI certification in Germany and DARE guidelines in the Netherlands with requirements specific to those networks removed. DRIVER partners involved in other repository networks, such as HAL in France and SHERPA in the UK, provided additional input to ensure that the DRIVER Guidelines are suitable for implementation by the entire European repository community. The DRIVER Guidelines are available from the %newwin%[[http://www.driver-support.eu/managers.html | Support website]]. A Wiki page has been set up for the [[DRIVERGuidelines|DRIVER Guidelines]] where you may contribute.
Changed lines 9-10 from:
The DRIVER Guidelines were developed based on the DINI certification in Germany and DARE guidelines in the Netherlands with requirements specific to those networks removed. DRIVER partners involved in other repository networks, such as HAL in France and SHERPA in the UK, provided additional input to ensure that the DRIVER Guidelines are suitable for implementation by the entire European repository community. The DRIVER Guidelines are available from the %newwin%[[http://www.driver-support.eu/en/guidelines.html | Support website]]. A Wiki page has been set up for the [[DRIVERGuidelines|DRIVER Guidelines]] where you may contribute.
to:
The DRIVER Guidelines were developed based on the DINI certification in Germany and DARE guidelines in the Netherlands with requirements specific to those networks removed. DRIVER partners involved in other repository networks, such as HAL in France and SHERPA in the UK, provided additional input to ensure that the DRIVER Guidelines are suitable for implementation by the entire European repository community. The DRIVER Guidelines are available from the %newwin%[[http://www.driver-support.eu/documents/DRIVER_guidelines_1%200.pdf | Support website]]. A Wiki page has been set up for the [[DRIVERGuidelines|DRIVER Guidelines]] where you may contribute.
Changed line 7 from:
Below are the topics we felt would be of interest to the community. As the wiki and this page develop we will add additional topics to reflect growing areas of interest. Do contact us with your suggestions mailto:helpdesk@driver-support.eu
to:
Below are the topics we felt would be of interest to the community. As the wiki and this page develop we will add additional topics to reflect growing areas of interest. Do contact us with your suggestions [[http://helpdesk.driver.research-infrastructures.eu | http://helpdesk.driver.research-infrastructures.eu ]]
Changed line 7 from:
Below are the topics we felt would be of interest to the community. As the wiki and this page develop we will add additional topics to reflect growing areas of interest. Do contact us with your suggestions mailto:info@driver-support.eu
to:
Below are the topics we felt would be of interest to the community. As the wiki and this page develop we will add additional topics to reflect growing areas of interest. Do contact us with your suggestions mailto:helpdesk@driver-support.eu
Changed lines 12-14 from:
DRIVER, the Digital Repository Infrastructure Vision for European Research is proud to announce the software release D-NET v. 1.0. The first of its kind, this open source software offers a tool-box for deploying a tool-box for deploying a customizable distributed system featuring tools for harvesting and aggregating heterogeneous data sources. A variety of end-user functionalities are applied over this integration, ranging from search, recommendation, collections, profiling to innovative tools for repository manager users. The official press release is available [[http://www.driver-repository.eu/DRIVER-News-Events/PR_D-NET_1_0.html | here]]. Please also see the [[DRIVER Infrastructure|Infrastructure]] section of this wiki for further details.
to:
DRIVER, the Digital Repository Infrastructure Vision for European Research is proud to announce the software release D-NET v. 1.0. The first of its kind, this open source software offers a tool-box for deploying a customizable distributed system featuring tools for harvesting and aggregating heterogeneous data sources. A variety of end-user functionalities are applied over this integration, ranging from search, recommendation, collections, profiling to innovative tools for repository manager users. The official press release is available [[http://www.driver-repository.eu/DRIVER-News-Events/PR_D-NET_1_0.html | here]]. Please also see the [[DRIVER Infrastructure|Infrastructure]] section of this wiki for further details.
Changed lines 11-14 from:
to:
!!DRIVER Infrastructure and D-NET
DRIVER, the Digital Repository Infrastructure Vision for European Research is proud to announce the software release D-NET v. 1.0. The first of its kind, this open source software offers a tool-box for deploying a tool-box for deploying a customizable distributed system featuring tools for harvesting and aggregating heterogeneous data sources. A variety of end-user functionalities are applied over this integration, ranging from search, recommendation, collections, profiling to innovative tools for repository manager users. The official press release is available [[http://www.driver-repository.eu/DRIVER-News-Events/PR_D-NET_1_0.html | here]]. Please also see the [[DRIVER Infrastructure|Infrastructure]] section of this wiki for further details.
DRIVER, the Digital Repository Infrastructure Vision for European Research is proud to announce the software release D-NET v. 1.0. The first of its kind, this open source software offers a tool-box for deploying a tool-box for deploying a customizable distributed system featuring tools for harvesting and aggregating heterogeneous data sources. A variety of end-user functionalities are applied over this integration, ranging from search, recommendation, collections, profiling to innovative tools for repository manager users. The official press release is available [[http://www.driver-repository.eu/DRIVER-News-Events/PR_D-NET_1_0.html | here]]. Please also see the [[DRIVER Infrastructure|Infrastructure]] section of this wiki for further details.
Changed lines 78-79 from:
Karen Van Godtsenhoven, Belgian DRIVER contact,
to:
Karen Van Godtsenhoven, Belgian DRIVER contact,\\
[[http://www.driver-repository.be | Belgian DRIVER website]]\\
[[http://www.driver-repository.be | Belgian DRIVER website]]\\
Changed lines 80-81 from:
to:
Karen dot VanGodtsenhoven at UGent dot be
Added lines 90-91:
%newwin%[[http://www.open-access.net/ | German Open Access Portal]]
Added lines 78-80:
Karen Van Godtsenhoven, Belgian DRIVER contact,
[[http://www.driver-repository.be | Belgian DRIVER website]]
[[http://www.driver-repository.be | Belgian DRIVER website]]
Changed lines 63-64 from:
The DRIVER Search service has been tested from September until November 2007 by about 80 researchers from three countries (UK, FR, BE) and the %newwin%[[http://www.driver-support.eu/documents/DRIVER_usability_study_Gent.pdf | usability report]] is now online. The survey was led by the University of Ghent and the outcomes were as follows:\\
* More than 60% would continue using the service, on the premise that the content grows continually
to:
The DRIVER Search service has been tested from September until November 2007 by about 80 researchers from three countries (UK, FR, BE) and the %newwin%[[http://www.driver-support.eu/documents/DRIVER_usability_study_Gent.pdf | usability report]] is now online. The survey was led by the University of Ghent and the outcomes were as follows:
*More than 60% would continue using the service, on the premise that the content grows continually
*More than 60% would continue using the service, on the premise that the content grows continually
Changed lines 62-63 from:
RESEARCHERS ASKED FOR THEIR OPINION: DRIVER USABILITY STUDY
The DRIVER Search service has been tested from September until November 2007 by about 80 researchers from three countries (UK, FR, BE) and the %newwin%[[http://www.driver-support.eu/documents/DRIVER_usability_study_Gent.pdf | usability report]] is now online. The survey was led by the University of Ghent and the outcomes were as follows:
to:
RESEARCHERS ASKED FOR THEIR OPINION: DRIVER USABILITY STUDY \\
The DRIVER Search service has been tested from September until November 2007 by about 80 researchers from three countries (UK, FR, BE) and the %newwin%[[http://www.driver-support.eu/documents/DRIVER_usability_study_Gent.pdf | usability report]] is now online. The survey was led by the University of Ghent and the outcomes were as follows:\\
The DRIVER Search service has been tested from September until November 2007 by about 80 researchers from three countries (UK, FR, BE) and the %newwin%[[http://www.driver-support.eu/documents/DRIVER_usability_study_Gent.pdf | usability report]] is now online. The survey was led by the University of Ghent and the outcomes were as follows:\\
Changed lines 62-65 from:
RESEARCHERS ASKED FOR THEIR OPINION:
The DRIVER Search service is due to go live in testing phase later this month. The European research community is being asked to participate in a usability survey of the new service. The survey is being led by the University of Ghent and offers researchers a chance to make a significant contribution to the development of this service.
Please let your academics know about this survey and contact mailto:info@driver-support.eu for further details.
Please let your academics know about this survey and contact mailto:info@driver-support.eu for further details
to:
RESEARCHERS ASKED FOR THEIR OPINION: DRIVER USABILITY STUDY
The DRIVER Search service has been tested from September until November 2007 by about 80 researchers from three countries (UK, FR, BE) and the %newwin%[[http://www.driver-support.eu/documents/DRIVER_usability_study_Gent.pdf | usability report]] is now online. The survey was led by the University of Ghent and the outcomes were as follows:
* More than 60% would continue using the service, on the premise that the content grows continually
*the user interface and search functionalities were perceived as satisfactory and efficient, many users asked for more user-specific ranking options
*the added value for most researchers was the free access to 'grey' lieterature such as conference proceedings and PHD theses
*multilingualism was not considered an important issue
* New developments as export functions, interactive functionalities and cross-referencing to other platforms were given priority by the users.
The DRIVER Search service has been tested from September until November 2007 by about 80 researchers from three countries (UK, FR, BE) and the %newwin%[[http://www.driver-support.eu/documents/DRIVER_usability_study_Gent.pdf | usability report]] is now online. The survey was led by the University of Ghent and the outcomes were as follows:
* More than 60% would continue using the service, on the premise that the content grows continually
*the user interface and search functionalities were perceived as satisfactory and efficient, many users asked for more user-specific ranking options
*the added value for most researchers was the free access to 'grey' lieterature such as conference proceedings and PHD theses
*multilingualism was not considered an important issue
* New developments as export functions, interactive functionalities and cross-referencing to other platforms were given priority by the users.
Added lines 88-89:
%newwin%[[http://www.sherpa.ac.uk/projects/sherparomeo.html | Sherpa/Romeo]]
Added lines 78-79:
%newwin%[[http://www.eua.be/index.php?id=396 | European University Association Working group on Open Access]]
Added lines 88-89:
%newwin%[[http://www.arl.org/sparc/ | SPARC, the Scholarly Publishing and Academic Resources Coalition]]
Added lines 78-79:
%newwin%[[http://lanic.utexas.edu/project/laoap/faq_esp.html | Latin America Open Archives Portal]].
Changed lines 84-85 from:
%newwin%[[http://lanic.utexas.edu/project/laoap/faq_esp.html | Latin America Open Archives Portal]].
to:
%newwin%[[http://sciencecommons.org/ | Science Commons]]
Added lines 78-79:
%newwin%[[http://www.openarchives.org/ |Open Archives Initiative]]
Changed lines 75-76 from:
to:
%newwin%[[http://amsci-forum.amsci.org/archives/American-Scientist-Open-Access-Forum.html | Archives of the American Scientist's Open Acces Forum]]
Changed lines 76-77 from:
to:
%newwin%[[http://www.earlham.edu/~peters/fos/ | Peter Suber's Open Access blog and Newsletter]]
Changed lines 76-77 from:
to:
%newwin%[[http://www.earlham.edu/~peters/fos/ | Peter Suber's Open Access blog and Newsletter]]
Added lines 36-37:
Added lines 76-77:
Peter Suber's Open Access blog and Newsletter [[http://www.earlham.edu/~peters/fos/]]
Changed lines 9-11 from:
The DRIVER Guidelines were developed based on the DINI certification in Germany and DARE guidelines in the Netherlands with requirements specific to those networks removed. DRIVER partners involved in other repository networks, such as HAL in France and SHERPA in the UK, provided additional input to ensure that the DRIVER Guidelines are suitable for implementation by the entire European repository community. The DRIVER Guidelines are available from the %newwin%[[http://www.driver-support.eu/en/guidelines.html | Support website]]. A Wiki page has been set up for the [[DRIVER Guidelines]] where you may contribute.
to:
The DRIVER Guidelines were developed based on the DINI certification in Germany and DARE guidelines in the Netherlands with requirements specific to those networks removed. DRIVER partners involved in other repository networks, such as HAL in France and SHERPA in the UK, provided additional input to ensure that the DRIVER Guidelines are suitable for implementation by the entire European repository community. The DRIVER Guidelines are available from the %newwin%[[http://www.driver-support.eu/en/guidelines.html | Support website]]. A Wiki page has been set up for the [[DRIVERGuidelines|DRIVER Guidelines]] where you may contribute.
Changed lines 9-11 from:
The DRIVER Guidelines were developed based on the DINI certification in Germany and DARE guidelines in the Netherlands with requirements specific to those networks removed. DRIVER partners involved in other repository networks, such as HAL in France and SHERPA in the UK, provided additional input to ensure that the DRIVER Guidelines are suitable for implementation by the entire European repository community. The DRIVER Guidelines are available from the %newwin%[[http://www.driver-support.eu/en/guidelines.html | Support website]]. A Wiki page has been set up for the [[Main/DRIVER Guidelines]] where you may contribute.
to:
The DRIVER Guidelines were developed based on the DINI certification in Germany and DARE guidelines in the Netherlands with requirements specific to those networks removed. DRIVER partners involved in other repository networks, such as HAL in France and SHERPA in the UK, provided additional input to ensure that the DRIVER Guidelines are suitable for implementation by the entire European repository community. The DRIVER Guidelines are available from the %newwin%[[http://www.driver-support.eu/en/guidelines.html | Support website]]. A Wiki page has been set up for the [[DRIVER Guidelines]] where you may contribute.
Changed lines 38-39 from:
In trying to populate a repository it can be more successful to concentrate on encouraging researchers to deposit their recent publications rather than asking them to deposit all their publications to date.
to:
In trying to populate a repository it can be more successful to concentrate on encouraging researchers to deposit their recent publications rather than asking them to deposit all their publications to date.
Added line 38:
In trying to populate a repository it can be more successful to concentrate on encouraging researchers to deposit their recent publications rather than asking them to deposit all their publications to date.
Added lines 29-33:
Embargoed papers:
Many repositories accept papers with embargoes. Researchers become frustrated if they try to access an article through a repository and find it is not available. Hence it is useful if embargoed papers can be 'hidden' until the embargo expires. The %newwin%[[http://e-thesis.sharelab.cq2.org/upload.view/ETD-dspace-embargo-handler.pdf |Leiden Tool]], was developed by the University of Leiden for their DSpace repository and allows embargoed papers to be 'hidden' until the embargo expires.
Are there similar tools for other repository softwares?
Added lines 17-24:
!!Repository Staff & Skills
In response to requests from the repository community, and with input from UKCoRR members, %newwin%[[http://www.sherpa.ac.uk|SHERPA]] has compiled a skills set and description of the common repository roles/jobs needed to develop and manage a UK institutional repository. The document can be found on the SHERPA [[http://www.sherpa.ac.uk/news/Aug2007-01.htm|website]].
How do institutions in other countries manage their repositories and are the same skills needed? Please give examples from your country.
In response to requests from the repository community, and with input from UKCoRR members, %newwin%[[http://www.sherpa.ac.uk|SHERPA]] has compiled a skills set and description of the common repository roles/jobs needed to develop and manage a UK institutional repository. The document can be found on the SHERPA [[http://www.sherpa.ac.uk/news/Aug2007-01.htm|website]].
How do institutions in other countries manage their repositories and are the same skills needed? Please give examples from your country.
Changed lines 9-10 from:
The DRIVER Guidelines were developed based on the DINI certification in Germany and DARE guidelines in the Netherlands with requirements specific to those networks removed. DRIVER partners involved in other repository networks, such as HAL in France and SHERPA in the UK, provided additional input to ensure that the DRIVER Guidelines are suitable for implementation by the entire European repository community. The DRIVER Guidelines are available from the %newwin%[[http://www.driver-support.eu/en/guidelines.html | Support website]].
to:
The DRIVER Guidelines were developed based on the DINI certification in Germany and DARE guidelines in the Netherlands with requirements specific to those networks removed. DRIVER partners involved in other repository networks, such as HAL in France and SHERPA in the UK, provided additional input to ensure that the DRIVER Guidelines are suitable for implementation by the entire European repository community. The DRIVER Guidelines are available from the %newwin%[[http://www.driver-support.eu/en/guidelines.html | Support website]]. A Wiki page has been set up for the [[Main/DRIVER Guidelines]] where you may contribute.
Changed lines 9-10 from:
The DRIVER Guidelines were developed based on the DINI certification in Germany and DARE guidelines in the Netherlands with requirements specific to those networks removed. DRIVER partners involved in other repository networks, such as HAL in France and SHERPA in the UK, provided additional input to ensure that the DRIVER Guidelines are suitable for implementation by the entire European repository community. The DRIVER Guidelines are available from the %newwin%[[http://www.driver-support.eu/en/guidelines.html | Support website]]. A Wiki page has been set up for the [[Main/ DRIVER Guidelines]] where you may contribute.
to:
The DRIVER Guidelines were developed based on the DINI certification in Germany and DARE guidelines in the Netherlands with requirements specific to those networks removed. DRIVER partners involved in other repository networks, such as HAL in France and SHERPA in the UK, provided additional input to ensure that the DRIVER Guidelines are suitable for implementation by the entire European repository community. The DRIVER Guidelines are available from the %newwin%[[http://www.driver-support.eu/en/guidelines.html | Support website]].
Changed lines 9-10 from:
The DRIVER Guidelines were developed based on the DINI certification in Germany and DARE guidelines in the Netherlands with requirements specific to those networks removed. DRIVER partners involved in other repository networks, such as HAL in France and SHERPA in the UK, provided additional input to ensure that the DRIVER Guidelines are suitable for implementation by the entire European repository community. The DRIVER Guidelines are available from the %newwin%[[http://www.driver-support.eu/en/guidelines.html | Support website]]. A Wiki page has been set up for the [[Main/DRIVER Guidelines]] where you may contribute.
to:
The DRIVER Guidelines were developed based on the DINI certification in Germany and DARE guidelines in the Netherlands with requirements specific to those networks removed. DRIVER partners involved in other repository networks, such as HAL in France and SHERPA in the UK, provided additional input to ensure that the DRIVER Guidelines are suitable for implementation by the entire European repository community. The DRIVER Guidelines are available from the %newwin%[[http://www.driver-support.eu/en/guidelines.html | Support website]]. A Wiki page has been set up for the [[Main/ DRIVER Guidelines]] where you may contribute.
Changed lines 8-10 from:
to:
!!DRIVER Guidelines
The DRIVER Guidelines were developed based on the DINI certification in Germany and DARE guidelines in the Netherlands with requirements specific to those networks removed. DRIVER partners involved in other repository networks, such as HAL in France and SHERPA in the UK, provided additional input to ensure that the DRIVER Guidelines are suitable for implementation by the entire European repository community. The DRIVER Guidelines are available from the %newwin%[[http://www.driver-support.eu/en/guidelines.html | Support website]]. A Wiki page has been set up for the [[Main/DRIVER Guidelines]] where you may contribute.
The DRIVER Guidelines were developed based on the DINI certification in Germany and DARE guidelines in the Netherlands with requirements specific to those networks removed. DRIVER partners involved in other repository networks, such as HAL in France and SHERPA in the UK, provided additional input to ensure that the DRIVER Guidelines are suitable for implementation by the entire European repository community. The DRIVER Guidelines are available from the %newwin%[[http://www.driver-support.eu/en/guidelines.html | Support website]]. A Wiki page has been set up for the [[Main/DRIVER Guidelines]] where you may contribute.
Deleted lines 18-23:
Researchers and other users of digital information systems have high expectations for the provision of digital content. Retrieval should be fast, direct, and versatile. Ideally, retrieval of full text should be just one click away. The current state of institutional repositories does not fully support these expectations. While many valuable services have been established to search and retrieve bibliographic records (metadata), the resource itself is sometimes hidden behind several intermediate pages; obscured by authorization procedures; not fully presented; or not retrievable at all.
DRIVER approaches this challenge by harvesting and processing the aggregated data and by working with service providers and developers of leading repository software. Repository managers can assist DRIVER by ensuring that their repositories are compliant with the DRIVER Guidelines.
Changed lines 57-58 from:
Cornelius Puschmann, [[http://www.dipp.nrw.de/ | DiPP Initiative]] / [[http://www.phil-fak.uni-duesseldorf.de/anglist3/Puschmann/ | University of Düsseldorf]], Germany
to:
Cornelius Puschmann, [[http://www.dipp.nrw.de/ | DiPP Initiative]] / [[http://www.phil-fak.uni-duesseldorf.de/anglist3/Puschmann/ | University of Düsseldorf]]
August 09, 2007, at 12:09 PM
by - typo in the URL of my personal page
Changed lines 57-59 from:
Cornelius Puschmann, DiPP Initiative / University of Düsseldorf, Germany
[[http://www.phil-fak.uni-duesseldorf.de/anglist3/Puschmann/ | U Düsseldorf]]
to:
Cornelius Puschmann, [[http://www.dipp.nrw.de/ | DiPP Initiative]] / [[http://www.phil-fak.uni-duesseldorf.de/anglist3/Puschmann/ | University of Düsseldorf]], Germany
Changed lines 39-41 from:
Are metadata-only records an issue for repositories in other countries?
to:
Are metadata-only records an issue for repositories in other countries?
RESPONSE: While I don't have any figures at hand, my impression is that the issue is essentially the same in other European countries. However, I don't think the decisive question is really whether or not a full text is in the repository, but whether or not it is accessible to the researcher. If content is OA, it should be possible to provide the same kind of one-click access to remote sources that exists for locally stored material. The real problem is content that is either not OA or not digital. As a researcher who manages almost all his research and reading digitally, I find references to non-digital sources increasingly frustrating, but clearly that's not really an issue that DRIVER or the OA community can solve.
The essential problem with non-OA content (and I know this doesn't apply to the repositories we are talking about here, as they are probably OA-only) is really that the facility helping me with retrieval (library catalogue, Google Scholar etc) doesn't "know" whether or not I'll have access to a given resource. That exact point was brought up last month at the PKP conference in Vancouver. Someone asked Anurag Acharya, the GS lead developer, if it wouldn't be possible to somehow discern between accessible and inaccessible search results. Anurag said that because it can't be determined with certainty whether or not a user will have access, GS takes the inclusive approach and shows sources where the full text may be unavailable, which is a frustrating experience for the researcher.
What is needed is a flag in the DOI and URN of a resource that indicates whether it is freely accessible. This information can only be reliably provided by the publisher, anything else would be incredibly tedious. Having a lot of meta-data-only records in your repository is fine as long as the user has access to everything. To him it won't really make a difference where the resource is stored.
-Cornelius Puschmann
RESPONSE: While I don't have any figures at hand, my impression is that the issue is essentially the same in other European countries. However, I don't think the decisive question is really whether or not a full text is in the repository, but whether or not it is accessible to the researcher. If content is OA, it should be possible to provide the same kind of one-click access to remote sources that exists for locally stored material. The real problem is content that is either not OA or not digital. As a researcher who manages almost all his research and reading digitally, I find references to non-digital sources increasingly frustrating, but clearly that's not really an issue that DRIVER or the OA community can solve.
The essential problem with non-OA content (and I know this doesn't apply to the repositories we are talking about here, as they are probably OA-only) is really that the facility helping me with retrieval (library catalogue, Google Scholar etc) doesn't "know" whether or not I'll have access to a given resource. That exact point was brought up last month at the PKP conference in Vancouver. Someone asked Anurag Acharya, the GS lead developer, if it wouldn't be possible to somehow discern between accessible and inaccessible search results. Anurag said that because it can't be determined with certainty whether or not a user will have access, GS takes the inclusive approach and shows sources where the full text may be unavailable, which is a frustrating experience for the researcher.
What is needed is a flag in the DOI and URN of a resource that indicates whether it is freely accessible. This information can only be reliably provided by the publisher, anything else would be incredibly tedious. Having a lot of meta-data-only records in your repository is fine as long as the user has access to everything. To him it won't really make a difference where the resource is stored.
-Cornelius Puschmann
Added lines 56-59:
Cornelius Puschmann, DiPP Initiative / University of Düsseldorf, Germany
[[http://www.phil-fak.uni-duesseldorf.de/anglist3/Puschmann/ | U Düsseldorf]]
Changed lines 42-43 from:
RESEARCHERS ASKED FOR THEIR OPINION
to:
RESEARCHERS ASKED FOR THEIR OPINION:
Changed lines 42-46 from:
to:
RESEARCHERS ASKED FOR THEIR OPINION
The DRIVER Search service is due to go live in testing phase later this month. The European research community is being asked to participate in a usability survey of the new service. The survey is being led by the University of Ghent and offers researchers a chance to make a significant contribution to the development of this service.
Please let your academics know about this survey and contact mailto:info@driver-support.eu for further details.
The DRIVER Search service is due to go live in testing phase later this month. The European research community is being asked to participate in a usability survey of the new service. The survey is being led by the University of Ghent and offers researchers a chance to make a significant contribution to the development of this service.
Please let your academics know about this survey and contact mailto:info@driver-support.eu for further details.
Changed lines 33-34 from:
In the UK very few repositories are full text only i.e. do not have any metadata-only records. The inclusion of metadata-only records causes difficulties for search services who find it difficult to distinguish between records that link to full text and those that do not. The retrieval of metadata-only records by searches is frustrating and disappointing for researchers.
to:
In the UK very few repositories (~10%) are full text only i.e. do not have any metadata-only records. The inclusion of metadata-only records causes difficulties for search services who find it difficult to distinguish between records that link to full text and those that do not. The retrieval of metadata-only records by searches is frustrating and disappointing for researchers.
Changed lines 17-23 from:
to:
The [[http://www.driver-support.eu/en/guidelines.html | DRIVER Guidelines]] are based on the DINI certification in Germany and DARE guidelines in the Netherlands with requirements specific to those networks removed. DRIVER partners involved in other repository networks, such as HAL in France and SHERPA in the UK, provided additional input to ensure that the DRIVER Guidelines are suitable for implementation by the entire European repository community.
Researchers and other users of digital information systems have high expectations for the provision of digital content. Retrieval should be fast, direct, and versatile. Ideally, retrieval of full text should be just one click away. The current state of institutional repositories does not fully support these expectations. While many valuable services have been established to search and retrieve bibliographic records (metadata), the resource itself is sometimes hidden behind several intermediate pages; obscured by authorization procedures; not fully presented; or not retrievable at all.
DRIVER approaches this challenge by harvesting and processing the aggregated data and by working with service providers and developers of leading repository software. Repository managers can assist DRIVER by ensuring that their repositories are compliant with the DRIVER Guidelines.
Across the EU the %newwin%[[http://www.driver-support.eu/documents/DRIVER Inventory study 2007.pdf |DRIVER Inventory study ]] found that of the repositories surveyed, the most frequently used repository software packages were GNU Eprints, DSpace, and OPUS.
Researchers and other users of digital information systems have high expectations for the provision of digital content. Retrieval should be fast, direct, and versatile. Ideally, retrieval of full text should be just one click away. The current state of institutional repositories does not fully support these expectations. While many valuable services have been established to search and retrieve bibliographic records (metadata), the resource itself is sometimes hidden behind several intermediate pages; obscured by authorization procedures; not fully presented; or not retrievable at all.
DRIVER approaches this challenge by harvesting and processing the aggregated data and by working with service providers and developers of leading repository software. Repository managers can assist DRIVER by ensuring that their repositories are compliant with the DRIVER Guidelines.
Across the EU the %newwin%[[http://www.driver-support.eu/documents/DRIVER Inventory study 2007.pdf |DRIVER Inventory study ]] found that of the repositories surveyed, the most frequently used repository software packages were GNU Eprints, DSpace, and OPUS.
Added lines 30-43:
METADATA-ONLY RECORDS- problems and potential
In the UK very few repositories are full text only i.e. do not have any metadata-only records. The inclusion of metadata-only records causes difficulties for search services who find it difficult to distinguish between records that link to full text and those that do not. The retrieval of metadata-only records by searches is frustrating and disappointing for researchers.
However the benefits of including metadata-only records must not be overlooked. Metadata-only records can allow the repository to act as a complete record of the research output of individual academics or of an institution. In the UK many repositories are now accepting metadata-only records to help with %newwin%[[http://www.rae.ac.uk/ |RAE]] process.
This issue is addressed by the DRIVER Guidelines through the inclusion of full text sets which will allow search and other service providers to distinguish between metadata-only records and those that link to full text.
Are metadata-only records an issue for repositories in other countries?
Changed lines 7-8 from:
Below are the topics we felt would be of interest to the community. As the wiki and this page develop we will add additional topics to reflect growing areas of interest. Do contact us with your suggestions mailto:driver@nottingham.ac.uk
to:
Below are the topics we felt would be of interest to the community. As the wiki and this page develop we will add additional topics to reflect growing areas of interest. Do contact us with your suggestions mailto:info@driver-support.eu
Changed lines 29-31 from:
(Share your favourite Open Access links here)
to:
(Share your favourite Open Access links here)
%newwin%[[http://lanic.utexas.edu/project/laoap/faq_esp.html | Latin America Open Archives Portal]].
%newwin%[[http://lanic.utexas.edu/project/laoap/faq_esp.html | Latin America Open Archives Portal]].
Changed lines 12-13 from:
DRIVER recently completed an "%newwin%[[http://www.driver-support.eu/documents/DRIVER Inventory study 2007.pdf |Inventory study into the present type and level of OAI compliant digital repository activities in the EU]]". The study which was managed by SURF, surveyed repository managers and associated institutional personnel on a range of issues relating to Open Access and repository development. Of the 27 EU countries, seven appear to have no institutional repositories, five are in the early stages of developing repositories while the remaining 15 countries have, to varying degrees, established institutional repositories.
to:
DRIVER recently completed an "%newwin%[[http://www.driver-support.eu/documents/DRIVER Inventory study 2007.pdf |Inventory study into the present type and level of OAI compliant digital repository activities in the EU]]". The study which was managed by SURF, surveyed repository managers and associated institutional personnel on a range of issues relating to Open Access and repository development. Of the 27 EU countries, seven appear to have no institutional repositories, five are in the early stages of developing repositories while the remaining 15 countries have, to varying degrees, established institutional repositories. A separate wiki has been set up for %newwin% [[http://www.pleiade.nl/wiki/index.php | comments relating to this study]].
Changed lines 12-13 from:
DRIVER recently completed an "[[http://www.driver-support.eu/documents/DRIVER_Inventory_study_2007.pdf |Inventory study into the present type and level of OAI compliant digital repository activities in the EU]]". The study which was managed by SURF, surveyed repository managers and associated institutional personnel on a range of issues relating to Open Access and repository development. Of the 27 EU countries, seven appear to have no institutional repositories, five are in the early stages of developing repositories while the remaining 15 countries have, to varying degrees, established institutional repositories.
to:
DRIVER recently completed an "%newwin%[[http://www.driver-support.eu/documents/DRIVER Inventory study 2007.pdf |Inventory study into the present type and level of OAI compliant digital repository activities in the EU]]". The study which was managed by SURF, surveyed repository managers and associated institutional personnel on a range of issues relating to Open Access and repository development. Of the 27 EU countries, seven appear to have no institutional repositories, five are in the early stages of developing repositories while the remaining 15 countries have, to varying degrees, established institutional repositories.
Added lines 11-13:
DRIVER recently completed an "[[http://www.driver-support.eu/documents/DRIVER_Inventory_study_2007.pdf |Inventory study into the present type and level of OAI compliant digital repository activities in the EU]]". The study which was managed by SURF, surveyed repository managers and associated institutional personnel on a range of issues relating to Open Access and repository development. Of the 27 EU countries, seven appear to have no institutional repositories, five are in the early stages of developing repositories while the remaining 15 countries have, to varying degrees, established institutional repositories.
Added lines 16-18:
Across the EU the DRIVER Inventory Study found that of the repositories surveyed, the most frequently used repository software packages were GNU Eprints, DSpace, and OPUS.
Changed lines 17-18 from:
!!Have your say
(Anything can go here but keep it clean:-))
to:
!!Have your say
(Anything can go here but keep it clean:-))
!!Contributor's contact details
(Here you may add your contact details if you wish)
Mary Robinson, European Development Officer, [[http://www.sherpa.ac.uk/staff.html#robinson | SHERPA]]
(Anything can go here but keep it clean:-))
!!Contributor's contact details
(Here you may add your contact details if you wish)
Mary Robinson, European Development Officer, [[http://www.sherpa.ac.uk/staff.html#robinson | SHERPA]]
Changed line 13 from:
!!Subject repositories
to:
!!Subject Repositories
Added lines 13-14:
!!Subject repositories
(Existing subject repositories and suggestions for the future)
(Existing subject repositories and suggestions for the future)
Changed lines 5-6 from:
Elsewhere on the wiki there are pages dedicated to individual countries. This page is intended to provide an area where general topics can be developed.
to:
Elsewhere on the wiki are pages dedicated to individual countries. This page is intended to provide an area where general topics can be developed.
Changed lines 5-6 from:
Elsewhere on the wiki there are pages dedicated to individual countries. This page is intended to provide an area where topics can be developed in general.
to:
Elsewhere on the wiki there are pages dedicated to individual countries. This page is intended to provide an area where general topics can be developed.
Changed lines 5-6 from:
Elsewhere on the wiki there are page's dedicated to individual countries. This page is intended to provide an area where topics can be developed in general.
to:
Elsewhere on the wiki there are pages dedicated to individual countries. This page is intended to provide an area where topics can be developed in general.
Deleted lines 2-3:
!!!What is the purpose of this wiki?
Changed lines 7-18 from:
Below are the topics we felt would be of interest to the community. As the wiki and this page develop we will add additional topics to reflect growing areas of interest. Do contact us with your suggestions mailto:driver@nottingham.ac.uk
to:
Below are the topics we felt would be of interest to the community. As the wiki and this page develop we will add additional topics to reflect growing areas of interest. Do contact us with your suggestions mailto:driver@nottingham.ac.uk
!!OA & Repository Developments Worldwide
(Current trends and initiatives from around the world or your suggestions for the future)
!!Repository Software & Associated Technologies
(Current state of development and suggestions for the future)
!!Advocacy & Awareness
(Strategies, difficulties and examples from around the world)
!!Have your say
(Anything can go here but keep it clean:-))
!!Links
(Share your favourite Open Access links here)
!!OA & Repository Developments Worldwide
(Current trends and initiatives from around the world or your suggestions for the future)
!!Repository Software & Associated Technologies
(Current state of development and suggestions for the future)
!!Advocacy & Awareness
(Strategies, difficulties and examples from around the world)
!!Have your say
(Anything can go here but keep it clean:-))
!!Links
(Share your favourite Open Access links here)
Changed lines 5-13 from:
The basic structure of
We suggest that individual country pages are left to the editorship of people within that country, with local knowledge to ensure its accuracy and relevance
As material develops in maturity or whether material has long-term interest or relevance, then this may be taken through into the main driver-support website.
We hope that this provides a useful and enjoyable tool for the European open access repository community. Do get in touch with us with any suggestions.
to:
As mentioned on the wiki homepage, the purpose of this wiki is to provide a home for community contributions from across Europe, to create a dynamic and updatable picture of open access activity in the EU.
Elsewhere on the wiki there are page's dedicated to individual countries. This page is intended to provide an area where topics can be developed in general.
Below are the topics we felt would be of interest to the community. As the wiki and this page develop we will add additional topics to reflect growing areas of interest. Do contact us with your suggestions mailto:driver@nottingham.ac.uk
Elsewhere on the wiki there are page's dedicated to individual countries. This page is intended to provide an area where topics can be developed in general.
Below are the topics we felt would be of interest to the community. As the wiki and this page develop we will add additional topics to reflect growing areas of interest. Do contact us with your suggestions mailto:driver@nottingham.ac.uk
Changed lines 9-13 from:
to:
We suggest that individual country pages are left to the editorship of people within that country, with local knowledge to ensure its accuracy and relevance.
As material develops in maturity or whether material has long-term interest or relevance, then this may be taken through into the main driver-support website.
We hope that this provides a useful and enjoyable tool for the European open access repository community. Do get in touch with us with any suggestions.
As material develops in maturity or whether material has long-term interest or relevance, then this may be taken through into the main driver-support website.
We hope that this provides a useful and enjoyable tool for the European open access repository community. Do get in touch with us with any suggestions.
Changed line 3 from:
!!Repostory Development Worldwide
to:
!!Repository Development Worldwide
April 25, 2007, at 06:54 PM
by - initial testing and setting up
Changed lines 4-7 from:
!!!what is the purpose of this wiki?!!!
the purpose of this wiki is to provide a home for community contributions from across Europe, to create a dynamic and updatable picture of open access activity in the EU.
The basic structure of the wiki -- showing different countries -- should remain intact. We have also put suggested headings underneath each country's page to try to get some degree of commonality across the different pages. However, beyond this, the information that is provided under each country is really up to the contributors. You might like to note the particular funding environment in your country, significant institutions or people that are working in your country, or the note any local, or international, conferences and or events that are being held.
the
The basic structure of the wiki -- showing different countries -- should remain intact. We have also put suggested headings underneath each country's page to try to get some degree of commonality across the different pages. However, beyond this, the information that is provided under each country is really up to the contributors. You might like to note the particular funding environment in your country, significant institutions or people that are working in your country, or the note any local, or international, conferences and or events that are being held.
to:
!!!What is the purpose of this wiki?
The purpose of this wiki is to provide a home for community contributions from across Europe, to create a dynamic and updatable picture of open access activity in the EU.
The basic structure of the wiki -- showing different countries -- should remain intact. We have also put suggested headings underneath each country's page to try to get some degree of commonality across the different pages. However, beyond this, the information that is provided under each country is really up to the contributors. You might like to note the particular funding environment in your country, significant institutions or people that are working in your country, or the note any local, or international, conferences and or events that are being held.
we suggest that individual country pages are left to the editorship of people within that country, with local knowledge to ensure its accuracy and relevance.
as material develops in maturity or whether material has long-term interest or relevance, then this may be taken through into the main driver-support website.
we hope that this provides a useful and enjoyable tool for the European open access repository community. Do get in touch with us with any suggestions.
The purpose of this wiki is to provide a home for community contributions from across Europe, to create a dynamic and updatable picture of open access activity in the EU.
The basic structure of the wiki -- showing different countries -- should remain intact. We have also put suggested headings underneath each country's page to try to get some degree of commonality across the different pages. However, beyond this, the information that is provided under each country is really up to the contributors. You might like to note the particular funding environment in your country, significant institutions or people that are working in your country, or the note any local, or international, conferences and or events that are being held.
we suggest that individual country pages are left to the editorship of people within that country, with local knowledge to ensure its accuracy and relevance.
as material develops in maturity or whether material has long-term interest or relevance, then this may be taken through into the main driver-support website.
we hope that this provides a useful and enjoyable tool for the European open access repository community. Do get in touch with us with any suggestions.
April 25, 2007, at 06:39 PM
by - what the wiki is for
Changed lines 3-7 from:
!!Repostory Development Worldwide
to:
!!Repostory Development Worldwide
!!!what is the purpose of this wiki?!!!
the purpose of this wiki is to provide a home for community contributions from across Europe, to create a dynamic and updatable picture of open access activity in the EU.
The basic structure of the wiki -- showing different countries -- should remain intact. We have also put suggested headings underneath each country's page to try to get some degree of commonality across the different pages. However, beyond this, the information that is provided under each country is really up to the contributors. You might like to note the particular funding environment in your country, significant institutions or people that are working in your country, or the note any local, or international, conferences and or events that are being held.
!!!what is the purpose of this wiki?!!!
the purpose of this wiki is to provide a home for community contributions from across Europe, to create a dynamic and updatable picture of open access activity in the EU.
The basic structure of the wiki -- showing different countries -- should remain intact. We have also put suggested headings underneath each country's page to try to get some degree of commonality across the different pages. However, beyond this, the information that is provided under each country is really up to the contributors. You might like to note the particular funding environment in your country, significant institutions or people that are working in your country, or the note any local, or international, conferences and or events that are being held.
Changed line 3 from:
to:
!!Repostory Development Worldwide
Added lines 1-3:
(:title General Open Access Topics:)
//Repostory Development Worldwide
//Repostory Development Worldwide
Page last modified: November 02, 2009, at 03:08 PM