This new version of the Guidelines, according to the expansion of the aims of the OpenAIRE initiative and its infrastructure, has a broader scope. In fact, these Guidelines are intended to guide repository manager to expose to the OpenAIRE infrastructure open access and non-open access publications together with funding information , where applicable.
By implementing these Guidelines, repository managers will not only be enabling authors who deposit publications in their repository to fulfill the EC Open Access requirements, and eventually also the requirements of other national or international funders with whom OpenAIRE cooperates, but also incorporating their publications into the OpenAIRE infrastructure for discoverability and utilizing value-added services provided by the OpenAIRE portal.
In comparison with previous versions of the Guidelines, this version introduces the following major changes:. Source: The source is used for development. This will usually originate from a source code repository, such as git. You can fetch this when you want to modify the downloaded package. Packages can supply either of these, or even both.
Depending on certain factors, such as user-supplied options and stability of the package, one will be preferred. A repository is a package source. Composer will look in all your repositories to find the packages your project requires. By default, only the Packagist. You can add more repositories to your project by declaring them in composer.
Repositories are only available to the root package and the repositories defined in your dependencies will not be loaded. Read the FAQ entry if you want to learn why. When resolving dependencies, packages are looked up from repositories from top to bottom, and by default, as soon as a package is found in one, Composer stops looking in other repositories.
Read the repository priorities article for more details and to see how to change this behavior. The main repository type is the composer repository. It uses a single packages. This is also the repository type that packagist uses. To reference a composer repository, supply the path before the packages.
For example. The composer. The notify-batch field allows you to specify a URL that will be called every time a user installs a package. The metadata-url field allows you to provide a URL template to serve all packages which are in the repository. This field is new in Composer v2, and is prioritised over the provider-includes and providers-url fields if both are present.
For compatibility with both Composer v1 and v2 you ideally want to provide both. New repository implementations may only need to support v2 however. Caching is done via the use of If-Modified-Since header, so make sure you return Last-Modified headers and that they are accurate. Any requested package which does not exist MUST return a status code, which will indicate to Composer that this package does not exist in your repository.
Make sure the response is fast to avoid blocking Composer. Avoid redirects to alternative pages. If your repository only has a small number of packages, and you want to avoid the requests, you can also specify an "available-packages" key in packages. The providers-api field allows you to provide a URL template to serve all packages which provide a given package name, but not the package which has that name. The list field allows you to return the names of packages which match a given field or all names if no filter is present.
It should accept an optional? The provider-includes field allows you to list a set of files that list package names provided by this repository. Nearly three years later, the new LA Referencia guidelines Interoperable Metadata and Harvest Policies for La Referencia National Nodes present and update the fields in a more detailed format, and provide recommendations for all the fields present in Driver.
They also offer clarifications and changes derived from OpenAIRE which currently maintains the guidelines and define the main areas to work in future releases. The main audience of the guidelines document are the eight national nodes in La Referencia. It is probable that some of these alignments depending on the field will be reached at the level of transformation in the node of La Referencia and in the national node. It is the largest initiative of its kind and is leading the way in supporting and enhancing repository development in Europe and indeed worldwide.
DRIVER makes possible the development of high-quality search and associated services for the research community, which will enable effective retrieval and use of content held in repositories. A unified European approach will also ensure that repositories and their use become an accepted part of research and research publication processes across Europe. It sets out to build a testbed for a future knowledge infrastructure of the European Research Area.
Within the DRIVER Project a number of strategic and co-ordinated studies on digital repositories and related topics have been carried out. It aims to motivate and promote the further creation, development and networking of repositories. It contains comprehensive and current information on digital repository-related issues particularly relevant to repository managers, decision makers, funding agencies and infrastructure services as stakeholders.
DRIVER has identified five specific, complex and long-term issues which are essential to the establishment, development or sustainability of a digital repository: the business of digital repositories; stimuli for depositing materials into repositories; intellectual property rights; data curation; and long-term preservation.
The success of a repository is dependent on having addressed these five issues sufficiently. Good practice and lessons learned as part of this report will assist stakeholders in both their day-to-day and long-term challenges, and can help them avoid reinventing the wheel. Special attention is paid to the interoperability of repositories to enhance the exchange of repository data.
The study is aimed at institutional repository managers, service providers, repository software developers and all players taking an active part in the creation of the digital repository infrastructure for e-research.
It aims to raise discussion on these topics and to support initiatives for the integration and in some cases the development of new standards, in addition to the current interoperability mechanisms that have been implemented in digital repositories.
The study not only looks at the current situation, but also at the near future: what steps should be taken now in order to support future demands? This study is also due to be published in December The landscape of digital repositories is multi-faceted with respect to different countries, different resources such as text, data or multimedia, different technological platforms, different metadata policies, etc.
However there is also a considerable degree of homogeneity across parts of this landscape: the main resource type provided by digital repositories is text see Figure 1 and the common approach for offering textual resources is via the Open Archives Initiative Protocol for Metadata Harvesting OAI-PMH. These resources are mainly articles, but also include lectures, theses, reports etc.
Direct access means that the user can download and use the full text of these resources with only a few clicks, anytime, anywhere, and without payment. As distributed systems, repository networks critically depend on interoperability in terms of technology and content provision. DAREnet [ 9 ], HAL [ 10 ] reveals firstly that homogenous use of the protocol considerably strengthens the quality of services for the end-user.
A number of additional issues around the use of the protocol have been defined and listed in Investigative Study of Standards for Digital Repositories and Related Services [ 8 ].
0コメント