2. What is Transfer?
A voluntary code for journal publishers
containing best practices for transferring and
receiving journals.
Governed by a standing committee of
librarians, publishers & other intermediaries
10. What to expect
•Publishers
• New log-in and credentials
•Librarians
• Automatic listserv migration
• RSS feed change
•All
• URL re-directs
11. Links
Transfer at NISO (NISO RP-24-2015)
https://www.niso.org/standards-committees/transfer
Transfer Notifications
https://www.niso.org/standards-committees/transfer/enhanced-transfer-alerting-service
Transfer-Endorsing Publishers
https://www.niso.org/standards-committees/transfer/transfer-publishers
I’m Jennifer Bazeley, and I’m here today on behalf of the committee that oversees the Transfer Code of Practice to give you a short introduction to Transfer but also to talk about some exciting changes coming later this year. Thank you to NISO and Todd and Nettie for allowing us to provide this update as part of NISO’s annual update session.
What is Transfer?
A voluntary code for journal publishers containing best practices for transferring and receiving journals. The code helps publishers to ensure that journal content remains accessible by librarians and readers when there is a transfer between parties, and ensures that the transfer process occurs with minimum disruption. Publishers who register as Transfer-compliant are asked to endorse the Code, and to abide by its principles wherever it is commercially reasonable to do so.
Best practices in the code include:
formalized roles/responsibilities for transferring and receiving publishers
timelines for transfer actions and communications
suggestions for transferring digital content and subscriber lists, guidance on handling identifiers and URLs
use of the Transfer alerting service
advice on existing licensing terms and preservation agreements
Currently working under version 3.0, finalized 2014/2015.
Transfer is governed by a standing committee which currently includes 7 publishers, 5 librarians and 7 intermediaries. The group is led by two co-chairs, one who is a publisher and one who is a librarian, and meets once every two months.
To date, the Transfer code of practice has more than 60 endorsing publishers, including CUP, Elsevier, NPG, OUP, Springer, T&F, Wiley.
We have two forthcoming updates that I want to address today.
Transfer Code of Practice v.4
First, the current version 3 of the code is being revised to accommodate changes in the journal publishing market, in technology, and in terminology. Some specific updates include:
Updates to terminology relating to journal purchasing models, especially in regard to open access publishing
Clarifications on using technology like URL re-directs when a journal transfer occurs
Updates to clauses dealing with “in process” articles to take into account the use of online editorial systems, which are used by almost all publishers
More inclusive language to ensure that supplemental content (not necessarily traditional articles) is also transferred; publishers may now be publishing more than just traditional articles; data sets and other materials that go hand in hand with an article also need to be transferred.
An updated and expanded glossary
Changes are meant to clarify legal and technological responsibilities of transferring and receiving publishers; and to help ensure that all publishers, regardless of how large or small they are, can comply with the code if they endorse it.
Revisions to the code have taken longer than expected and have been recently delayed by a discussion of the impact of GDPR on the code. However, the Transfer committee hopes to publish a draft of version 4 for public comment over this summer; please keep an eye on professional listservs and the NISO site for the announcement. We welcome feedback from all stakeholders on the potential revisions.
Second, we are migrating the Transfer Alerting Service
The TAS is in the process of being moved from the UK’s JISC servers to the ISSN Centre’s servers, where it will become integrated with the ISSN Centre portal. The committee is currently reviewing a beta test version of the migrated alerting service and hopes to roll out the new site for everyone by the end of the summer. The next few slides provide a preview of what the interface will look like plus some exciting new features!
The transfer alerting service is a database of information about journals moving from one publisher or vendor to another.
Transfer compliant publishers submit basic metadata about transferring journals to the Transfer Alerting Service. Submissions can be done title by title or through a bulk upload process. This metadata is stored in a searchable database and also disseminated via an e-mail listserv or RSS feed.
This slide shows a screenshot of what the new TAS home page will look like. Much of the look and feel and functionality will remain the same:
If you’re a publisher, the TAS site will allow you to submit journal transfers to the database
If you’re a librarian, the TAS site will allow you to search or browse journal transfers and to subscribe to the TAS RSS feed or e-mail listserv
One noted change to the site is that it will be available in both French and English rather than only English.
Search functionality will be similar to current functionality and will allow for filtering by date and a variety of search results sort options.
Search results will look similar but will include a new feature—a left-hand pane with facets that will allow you to filter your search results by receiving or transferring publisher.
ISSNs in search results will be hyperlinked to the corresponding entry or entries in the ISSN Centre portal.
Search results can also be exported into TSV format and opened in Excel.
Browsing is again similar to current functionality.
You can see several title results in this browse view—clicking on the title itself takes you to the transfer details; a new feature is clicking on the ISSNs—those links will go to the journal entry or entries in the ISSN Center portal, where you can see some additional information about the title.
Another change to the site will be easily accessible information about the TAS API. While the API has been around for a little while now, the details for using it were not easy to find online. The new site will have a direct link to this API page in the navigation banner at the top of the screen. The page will provide the baseURL, filters, keys, and values, and an example.
The ISSN Center has also created a few brand new features with the migration to their servers. There will be a page that lists successive transfers; this refers to any title that has had more than one transfer since the inception of the database in 2009. We hope this will be helpful especially to librarians when looking to trace the platform and publisher history for a particular title. Currently, this page is set up to automatically populate based on ISSNs and is not yet searchable.
A second new feature will be transfer statistics that can be viewed by anyone accessing the database. The ISSN Center has added a page that compiles statistics in graphical formats and will include graphs for number of transfer alerts per month and number of effective transfers per receiving and transferring publishers. All of the information in the graphs will be hyperlinked; clicking on one of the publishers in this example will open the search interface and display all of the Transfer entries indicated for that publisher.
For publishers: publishers who have Transfer accounts will begin logging in to the ISSN Centre after the migration happens. An ISSN International Centre account and credentials will be required (instead of the specific Transfer credentials you use now in the UK system). For publishers who are already registered with ISSN, they will use the same account. For those not registered yet, instructions will be provided to create an account. For now, no bulk uploads will be available, only title by title submissions. We expect bulk uploading to be added as an option this year, however.
For librarians: information will be sent out to multiple library listservs with information about the migration; if you are currently registered for the Transfer listserv, you will also receive an email at that address with migration information. Listserv recipients will be automatically migrated to the new servers; there will be no need to sign up again. The format of the emails will change a bit but the information provided will be the same. If you use the RSS feed, note that it will be maintained, but set-up details will change and re-directs will not be available—you’ll need to update your RSS feeds after the migration.
All: A URL re-direct will be established once the move occurs.
Here are a few links to Transfer materials that you may find useful:
Note that NISO migrated to a new website last year and URLs have changed slightly; if you have bookmarks saved in your browser, you may need to update them.
The first link goes to the general NISO Transfer page. Keep an eye on this page for updates about the code and the migration of the transfer alerting service.
The second link will direct you to information about the types of Transfer notifications I discussed today.
The final link provides a list of the publishers who currently endorse the Transfer code of practice.
Please feel free to direct any questions or concerns about anything I discussed today to the Transfer committee co-chairs, who are myself and James Phillpotts, of Oxford University Press.
https://journaltransfer.issn.org/transfer/search_transfer
Username : transtester
Password : N35bkt79