Hi Adam,

It might be helpful for me to clarify that GOKb is a two-year project (not
one year as the article states), and our first public release is scheduled
for the end of August. We are still in the process of establishing
relationships with other knowledge base products, and we are currently
developing a partnership model that will allow commercial entities to
become data contributors to GOKb. We're hopeful that commercial knowledge
base vendors will be interested in contributing elements of their data,
particularly proprietary identifiers for packages, titles, and holdings.
Having this data in GOKb would allow users to map data across systems,
facilitating not just interoperability between GOKb and other knowledge
bases, but also between various commercial products. GOKb has been in
dialogue with vendors such as EBSCO, ExLibris, OCLC and Serials Solutions
to this end.

We're also interested to know what you and the rest of the Code4Lib
community think about the potential for GOKb to interoperate with other
systems. Are there other ways you'd like to see this put into practice?

Best,

Kristen Wilson
Associate Head, Acquisitions and Discovery
GOKb Editor
North Carolina State University Libraries
919-513-3354
[email protected]


*From: *"Adam L. Chandler" <[email protected]>
> *Subject: **[CODE4LIB] Interoperability with GOKB*
> *Date: *28 July 2014 19:29:54 BST
> *To: *[email protected]
> *Reply-To: *Code for Libraries <[email protected]>
>
> "GOKb is expected to interoperate with other knowledge bases and linking
> environments." (*
> http://www.librarytechnology.org/ltg-displaytext.pl?RC=18671)
>
> Marshall Breeding made that assertion in September 2013.  What evidence
> exists to suggest that GOKb will be "interoperable"  with the
> knowledgebases of Ex Libris, Proquest, ExLibris, and OCLC?
>
>
> Thanks,
>
> Adam Chandler
> Technical Services Automation and User Experience Strategist
> Cornell University Library
> 107B Olin Library
> Ithaca, NY 14853
> 607-255-5760
> [email protected]
> https://twitter.com/alc28
>
>

Reply via email to