Automated Article-Deposit FAQ
- What is Automated Article-Deposit?
- Is my repository compatible with the SWORD protocol?
- How often will the article be deposited into the institutional repository?
- Where will the article go once it is sent to a repository?
- How will it be determined which articles are deposited in a particular institutional repository?
Automated Article-Deposit populates institutional repositories remotely via the SWORD (Simple Web-service Offering Repository Deposit) protocol and transfers complete article content (including PDFs, additional files and article metadata) from one repository to another. The SWORD vision is 'lowering the barriers to deposit', principally for depositing content into repositories, but potentially for depositing into any system which wants to receive content from remote sources.
It aids customers by automatically populating their institutional repositories with newly published articles from their researchers, from BioMed Central and SpringerOpen journals.
The SWORD protocol service has been designed to work with all major repository platforms, e.g. DSpace, eprints, Fedora, and we will continue to test and develop the service to ensure this is the case. The key point is that the repository is able to run SWORD feeds 1.3 - as long as this is the case then SWORD feeds can be integrated for your repository, no matter the vendor.
24 hours after an article is published in its final form (articles are transferred on a nightly basis).
Once an institution has adopted Automated Article-Deposit, the Repository Administrator can set up a desired 'end destination' for all articles that are fed in by the service. This can either go into a workflow for the Repository Administrator who can then allocate a specific collection for the article to be stored, or directly into an allocated collection within the repository.
We map articles to institutions using the same combination of affiliation information, email address stems, and institutional membership payment/discount data that is used to generate our institutional member pages. We work with institutions to ensure that this mapping is as accurate as possible, but institutions can use their own repository workflow to double-check and approve articles before they appear on their IR.