LISTSERV mailing list manager LISTSERV 16.0

Help for BIBFRAME Archives


BIBFRAME Archives

BIBFRAME Archives


BIBFRAME@LISTSERV.LOC.GOV


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

BIBFRAME Home

BIBFRAME Home

BIBFRAME  February 2016

BIBFRAME February 2016

Subject:

Re: creating/writing bibframe data

From:

Eric Lease Morgan <[log in to unmask]>

Reply-To:

Bibliographic Framework Transition Initiative Forum <[log in to unmask]>

Date:

Fri, 19 Feb 2016 15:15:34 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (49 lines)

On Feb 19, 2016, at 1:12 PM, Joy Nelson <[log in to unmask]> wrote:

> ...In our system we store marc as marc and as marcxml.  In my initial thoughts into this process, I'm wondering if the system just needs to become more 'agnostic' in the data format.  If I provide BIBFRAME in RDF/XML then the system should be able to pull out the bits it needs for display.  We would need some logic in the innerworkings to deal with various types of XML data.  And using an indexer on the system that can handle various XML formats would help in searching by users.  (I'm thinking Elastic Search here).   Right now I tend to think of the BIBFRAME descriptions as distinct units that would be similar to a marcxml record.  It is concievable to think that there would be an additional layer on top that would store ALL the triples and use some kind of SPARQL querying/searching???  I don't know about that yet.  An ILS has need for relational database structure since it is transactional.  But...could there be  component that is a graph database???…


Very interesting. Thank you, and based on this input, I’ve outlined a possible workflow for creating, maintaining, and exposing bibliographic description in the form of BIBFRAME linked data:

  1. Answer the questions, "What is bibliographic
     description, and how does it help facilitate the goals
     of librarianship?"

  2. Understand the concepts of the Semantic Web,
     specifically, the ideas behind Linked Data.

  3. Embrace & understand the strengths & weaknesses of
     BIBFRAME as a model for bibliographic description.

  4. Design or identify and then install a system for
     creating, storing, and editing your bibliographic data.
     This will be some sort of database application whether
     it be based on SQL, non-SQL, XML, or a triple store. It
     might even be your existing integrated library system.

  5. Using the database system, create, store, import/edit
     your bibliographic descriptions. For example, you might
     simply use your existing integrated library for these
     purposes, or you might transform your MARC data into
     BIBFRAME and pour the result into a triple store.

  6. Expose your bibliographic description as Linked Data
     by writing a report against the database system. This
     might be as simple as configuring your triple store, or
     as complicated as converting MARC/AACR2 from your
     integrated library system to BIBFRAME.

  7. Facilitate the discovery process, ideally through
     the use of a triple store/SPARQL combination, or
     alternatively directly against integrated library
     system.

  8. Go to Step #5 on a daily basis.

  9. Go to Step #1 on an annual basis.

If the profession continues to use its existing integrated library systems for maintaining bibliographic data (Step #4), then the hard problem to solve is transforming and exposing the bibliographic data as linked data in the form of BIBFRAME. If the profession designs a storage and maintenance system rooted in BIBFRAME to begin with, then the problem is accurately converting existing data into BIBFRAME and then designing mechanisms for creating/editing the data. I suppose the later option is “better”, but the former option is more feasible and requires less retooling.

—
Eric Lease Morgan

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
July 2011
June 2011

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager