As of next week, all http requests to the MPG/SFX link resolver will be redirected to a corresponding https request.
The Max Planck Society electronic Book Index is scheduled to be switched to https only access the week after, starting on November 27, 2017.
Regular web browser use of the above services should not be affected.
Please thoroughly test any solutions that integrate these services via their web APIs.
Please consider re-subscribing to MPG.eBooks RSS feeds.
Over the last years, many academic publishers introduced web syndication formats like RSS and Atom to provide their users with Table of Contents (TOC) alerting services. Due to the wide adoption of feed formats in the web, this trend promotes metadata reuse in many ways:
- Individual users may subscribe to TOC feeds in a reader client to receive information about recent publications. They can also apply web tools (like xfruits) to aggregate feeds and convert them to another message format.
- Website owners may use syndication services to dynamically integrate article information into their applications. For an example, check the homepage of the National Library of Health Sciences at the University of Helsinki (FeedNavigator boxes).
How to discover TOC feeds without searching each publisher’s homepage one after another? The ticTOCs project collected more than 12,000 journal feeds from over 400 publishers and offers an intuitive web interface on the top. In addition, the project team was broad-minded enough to share the source data with the community in order to ensure that journal feeds "osmose" into as many environments as possible. This strategy proved to be successful: the ticTOCs data is reused by numerous systems, including OCLC’s xISSN service, a Google application as well as library catalogs at Jönköping University or Wageningen UR …
… and finally we managed to load the data into the MPG/SFX link resolver as well, see http://tinyurl.sfx.mpg.de/q4r3 for an example:
However, one question remains: What will happen to the ticTOCs service now – after project end? Ed Pentz announced in the CrossRef Quarterly from May 2009 that "CrossRef is now investigating hosting the service on an ongoing basis", see version cached by Google. Currently, the ticTOCs homepage lacks an option to report problems or corrections, so the service manly relies on harvesting publisher websites. Will this be enough to keep the service up-to-date and unambiguous?
There had been two major usage scenarios which motivated us to introduce various RSS feeds for vLib resource lists about a year ago:
- Updating individual users about new resources available in the Max Planck Society
- Enabling MPG librarians or developers to re-use the resource information available in the vLib portal
Our experiences show that the first use case is pretty obvious to most vLib users while the second requires a lot more explanation… but we are willing to share! Check out the revised documentation of the vLib Resource Feeds to get some ideas and working examples.
vLib information resources are available in RSS 2.0 format, see http://vlib.mpg.de/vlib-rss-feed.html
What’s the benefit of this? A news stream to hook interest? A huge list of entry points to be filtered and maintained in a user’s own environment?
As items basically consist of a title, a description and a link, crucial information about the vLib resource represented by an RSS 2.0 item may fail to be conveyed.
This may be a mere mapping issue as discussed at https://devtools.mpdl.mpg.de/projects/vlib/wiki/RSS (i.e. map more fields to RSS 2.0 item description) – where we are not taking into account additional atom elements yet (to contain, for example, an html-formatted description), or atom format to contain more detailed data about a resource.
Or we might even consider pointing subscribers to our own interface to a resource rather than to the resource’s original web interface.
The vLib resource interface URL is actually present within items as guid, and, in fact, it is meant to be a permalink – however, certain feed readers appear to prefer a permalink in guid to the URL in item link, that’s why guid isPermaLink is presently set to false.