PKP Bugzilla – Bug 4148
Data request in journal setup
Last modified: 2013-05-29 15:32:46 PDT
To assist journals in increasing their visibility, we could add a setup step (3.x?) offering to collect their basic information and share it on our journal listing page (http://pkp.sfu.ca/ojs-journals) and with other libraries via their link resolver vendors (CUFTS, Serials Solutions, EBSCO, etc.).
Getting included in vendor link resolver lists would be an easy way for our journals to be included in many library collections.
Data fields would include:
- journal title
- journal archive URL
- ISSN and/or e-ISSN
- Starting date of available fulltext (e.g., 2007-12-31)
- Ending date of available fulltext (if applicable -- i.e., archived collections)
- Starting volume number of available fulltext
- Ending volume number of available fulltext (if applicable)
- Starting issue number of available fulltext
- Ending issue number of available fulltext (if applicable)
- Open Access Content (Y/N)
- Embargo period (in days)
- Publisher Name
- Contact Name
- Contact Email
- Languages (semi-colon separated)
Much of this could probably be generated automatically from existing data fields in the journal, and the setup step might only need to consist of an explanation and a Yes/No button to release the information.
Related to this, could a form be added about the type of journal being run? e.g. Gradate Student Journal. If Journal managers agree, this information, along with information like Contact Name, date of last issue published, etc. could be sent back to PKP home-base. This information could be automatically sent ever Sept 1, Jan 1, & May 1). The purpose of this PKP having this information is to facilitate coordination between related journals (e.g., all grad student journals could be listed on one page) and to monitor journals that may be inactive (e.g., haven't published in 8 months) and who might very much welcome reminder emails like ('At conferences you go to, there's often sessions for journal publishers... Or talk with peers at grad student journals)
*** This bug has been marked as a duplicate of bug 8188 ***