Coming at it from the ONIX point of view the recent JISC Project TOCRoSS
'Table of Contents by Really Simple Syndication'
[http://www.jisc.ac.uk/whatwedo/programmes/programme_pals2/project_tocro
ss.aspx] is an interesting example of automated distribution TOC
information.
There were two major deliverables from the project - a partnership
between Talis, Emerald Group Publishing, and the University of Derby.
First, was a provisional standard which embedded journal tables of
content and article level information [as per the ONIX SRN standard] in
to an RSS format. [example TOCRoSS feed output:
http://www.emeraldinsight.com/info/RSSFeeds/DerbyInsightFeeds/acmm_tocro
ss.xml]
The second was the development of an open source server which monitors
several of these feeds, as would be hosted for example by a publisher,
and provides output suitable for importing in to a library catalogue or
any other system. The architecture of the server is such that it is
easy to produce 'plug-in' modules to interface to the local system of
your choice.
The final outcome was that by monitoring TOCRoSS feeds hosted by
Emerald, the University of Derby catalogue is automatically populated
with journal article information for the titles they subscribe to.
Under the hood this is achieved with an ONIX to Marc21 crosswalk
implemented in a server module created to interface to their local
[Talis] library system import mechanism.
Not only did this project demonstrate the value of building upon
currently available standards, but also the power of using transport
protocols such as RSS to drive automated information distribution. The
bottom line for Derby is that they have their journals articles
catalogued, a task they could not have envisaged approaching if they had
to do it manual.
I'm sure this approach is not limited to just journal tables of content.
Richard Wallis
Technology Evangelist, Talis
Tel: +44 (0)870 400 5422 (Direct)
Tel: +44 (0)870 400 5000 (Switchboard)
Tel: +44 (0)7767 886 005 (Mobile)
Fax: +44 (0)870 400 5001
IM: rjw3226_at_hotmail.com
I-Name: =Richard.Wallis
> -----Original Message-----
> From: Next generation catalogs for libraries
> [mailto:NGC4LIB_at_listserv.nd.edu] On Behalf Of Zemon, Candy
> Sent: 30 January 2007 13:13
> To: NGC4LIB_at_listserv.nd.edu
> Subject: Re: [NGC4LIB] Tables of content
>
> And as memory serves, ONIX is another vehicle that carries
> this information in ways that promote its automated use. The
> idea is not bad
> - using this information in ways not well supported in the
> transport system MARC. The fun part is how to transport and
> then use the data in ways that make sense - preferably in
> standards-based ways so code is not provincial, proprietary,
> or one-use-only.
>
> And I doff an imaginary hat at the many standards whose time
> was not "right" at the point they were made. But the
> underlying ideas, if they are good ones, or more importantly,
> the underlying problems, if they are persistent ones, live on.
>
> Candy Zemon
> Senior Product Strategist
> Polaris Library Systems
> candy.zemon_at_polarislibrary.com
> 315-506-1611
> www.techtidbits.info
> -----Original Message-----
> From: Next generation catalogs for libraries
> [mailto:NGC4LIB_at_listserv.nd.edu] On Behalf Of Ted Koppel
> Sent: Monday, January 29, 2007 10:11 PM
> To: NGC4LIB_at_listserv.nd.edu
> Subject: Re: [NGC4LIB] Tables of content
>
> Judith,
>
> Great ideas all - and might I say, about eleven years late.
> In the mid 1990s, as an outgrowth of the SICI (Z39.56)
> standard, work was begun on a similar and self-derivable item
> identifier for pieces within a book.
> It was called the BICI (Book Information Component Identifier
> or something like that). See the following URL for a short
> description:
> http://cendi.dtic.mil/presentations/ref_link_blixrud.ppt.
>
> It went exactly nowhere. We finished a draft standard, but
> this took place at a time when DOI was in its ascent and
> BICIs were seen as old technology, despite their obvious
> benefits in self derivability, ability to make hierarchical
> connections, and so on. Bottom line: nothing official ever
> became of the BICI. (There were other issues as well, but
> nothing insurmountable.)
>
> Still, as an answer to your quest: "describing parts that
> have their own bibliographic integrity ... To spawn child
> records with appropriate connections to parents" - the BICI
> might be worth a second look.
>
> No good deeds every go to waste....
>
> Ted
>
>
> -----Original Message-----
> From: Next generation catalogs for libraries
> [mailto:NGC4LIB_at_listserv.nd.edu] On Behalf Of Judith Pearce
> Sent: Monday, January 29, 2007 8:16 PM
> To: NGC4LIB_at_listserv.nd.edu
> Subject: [NGC4LIB] Tables of content
>
> While time travelling on this list I noticed a discussion on
> how to encode tables of content in MARC records to support
> controlled access to authors of the listed parts. I've been
> mulling over this issue for some time in relation to our
> still image and audio digitisation projects.
> When it comes to describing parts that have their own
> bibliographic integrity I don't think trying to put this data
> in a note field is the way to go.
>
> In our new generation catalogues, why don't we throw tables
> of contents in records away, start giving parts of things
> their own records and express parent-child relationships in
> forms that enable users to navigate up and down bibliographic
> hierarchies and that enable the generation of tables of
> content dynamically in displays of the parent record.
>
> Why not encode and share tables of content and other lists in
> a form that can be used to spawn child records that inherit
> parent details in the appropriate fields and not bother
> storing this information in the parent record at all.
>
> This would make us look more closely at the information that
> needs to be stored in the child record and the information
> that can be inherited from the parent to create a full
> bibliographic citation.
>
> It would also make us look at ways of making the encoded
> relationship persistent when metadata is shipped to other
> places - union catalogues, federated metadata repositories,
> Google. Blogs, bibliographies.
>
> And it would make us look at ways of encoding the
> bibliographic citation so that the content inherited from the
> parent is not lost on export and the relationships can be
> fully exploited in the new context. I know OpenURL and the DC
> Citation working group have been working on this problem.
>
> This thinking can be extended to manuscript and archive
> collections, where we tend to treat the finding aid as a
> table of contents to the whole collection. When a whole
> collection (or an item in a collection) is digitised, there's
> a need to support component level searching and bibliographic
> citation.
>
> (How to handle parent-child relationships consistently and in
> a user-friendly way is still a real issue in our own
> production systems.
>
> http://nla.gov.au/nla.cat-vn3769891 is the best we can do
> with Voyager.
> Nuff said.
>
> http://nla.gov.au/anbd.bib-an40661746 is the same record in
> the Australian union catalogue. The direct parent-child
> relationship is lost because it was invoked by a local system
> number. The relationship has been expressed as a series,
> which is certainly not FRBR correct and the link retrieves
> all the bibliographic records with the same series authority,
> not the parent record.
>
> http://nla.gov.au/nla.ms-ms9803-1-13 - the same record in our
> digital delivery system. It gives a full bibliographic
> citation with item number and series details from the finding
> aid and enables navigation up and down the hierarchy through
> breadcrumbs.)
>
> Judith
>
> Judith Pearce
> Director, Feasibility & Standards
> National Library of Australia
> CANBERRA ACT 2600
> phone: +61 2 62621425
> email: jpearce_at_nla.gov.au
>
> --
> This message has been scanned for viruses and dangerous
> content by MailScanner, and is believed to be clean.
>
>
> --
> This message has been scanned for viruses and dangerous
> content by MailScanner, and is believed to be clean.
>
The very latest from Talis
read the latest news at www.talis.com/news
listen to our podcasts www.talis.com/podcasts
see us at these events www.talis.com/events
join the discussion here www.talis.com/forums
join our developer community www.talis.com/tdn
and read our blogs www.talis.com/blogs
Any views or personal opinions expressed within this email may not be those of Talis Information Ltd. The content of this email message and any files that may be attached are confidential, and for the usage of the intended recipient only. If you are not the intended recipient, then please return this message to the sender and delete it. Any use of this e-mail by an unauthorised recipient is prohibited.
Talis Information Ltd is a member of the Talis Group of companies and is registered in England No 3638278 with its registered office at Knights Court, Solihull Parkway, Birmingham Business Park, B37 7YB.
Received on Tue Jan 30 2007 - 09:12:47 EST