Hi! This is fantastic!
Assuming this can become a major reference for the community, I have two
pragmatic suggestions:
1- Please make it possible for third parties to import your data in XML (this
way we could find a way to reuse it automatically in our Institutional
Repository -I already identified several attributes in your data that would be
of great help to automate our process -and would avoid us to have to
scrap/parse your HTML for the same purpose ;-)
2- Please assure that you can keep a persistent syntax for your URLs, so we
can link back to them (and the minimum to acknowledge your service as a
source)! The actual syntax looks fine and effective... I just would like to
stress you to keep it stable, please.
Finally, I have a question back to you: assuming that this kind of information
also needs to be maintained in some local IRs (as it is our case, in the
system we are building in this precise moment...), maybe it would make sense
the community (you???) to define a standard way to exchange this information,
so you could get back from us updates and new records (maybe we can all agree
on something simple for that based on a data set to expose in our OAI-PMH
servers and using your own data schema for reference -the same I'm asking you
to expose in my point 1 up ;-)
Best Regards
José Borbinha
PS: this is really very helpful... THANK YOU!!!
-----Original Message-----
From: Repositories discussion list [mailto:[log in to unmask]]
On Behalf Of Peter Millington
Sent: Friday, October 29, 2010 2:34 PM
To: [log in to unmask]
Subject: New SHERPA/RoMEO Journals Database
*** Apologies for cross posting ***
RoMEO has been building its own database of journals for the publishers it
lists, with two main aims:
1. To identify journal titles more accurately with their publishers
2. To include journals that are not currently covered by the external look-up
databases that RoMEO uses
The work has been proceeding well. Over 95% of RoMEO publishers have been
processed, yielding nearly 18,000 journal titles (although this includes a few
duplicates). We are currently checking the quality of the data, and updating
the RoMEO search interface.
You are invited to try the latest prototype of the upgraded interface at:
http://www.sherpa.ac.uk/romeo/index34.php
Please remember that this is a prototype and is liable to change. It has not
yet been optimised for speed. It displays real data, but some information such
as alternative journal titles may not yet be visible. Upgrading the API will
follow later.
There are two things that you are likely to notice:
a. There is a new row in the RoMEO publisher details for journals.
e.g. "Journals: 276 journals - involving 129 other organisations - Source
journal list."
Here, "276 journals" links to the list of journals we have for the
publisher, and "Source journal list" links to the publisher's own list of
journals. "Other organisations" are the partners that the publisher works
with.
Currently, the journals for most imprints are listed under their parent
publisher rather than under their own name (e.g. Routledge and Taylor &
Francis). However, we are working to improve this.
b. Many journals now list two or more 'publishers' - for instance a publishing
house and its client scholarly society. This may be confusing, especially
where there are different archiving policies for each of the organisations. We
are working to improve this situation by eliminating unnecessary information
and providing guidance where appropriate.
We would welcome feedback on the prototype, either as comments on the
SHERPA/RoMEO Blog (http://romeo.jiscinvolve.org/wp/), or by email to
[log in to unmask]
Peter Millington
SHERPA Technical Development Officer
Centre for Research Communications
Greenfield Medical Library, University of Nottingham, Queen's Medical Centre,
Nottingham, NG7 2UH, England
This message and any attachment are intended solely for the addressee and may
contain confidential information. If you have received this message in error,
please send it back to me, and immediately delete it. Please do not use,
copy or disclose the information contained in this message or in any
attachment. Any views or opinions expressed by the author of this email do
not necessarily reflect the views of the University of Nottingham.
This message has been checked for viruses but the contents of an attachment
may still contain software viruses which could damage your computer system:
you are advised to perform your own checks. Email communications with the
University of Nottingham may be monitored as permitted by UK legislation.=
|