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  January 2017

BIBFRAME January 2017

Subject:

Re: How to describe complexities with bf:AccessPolicy?

From:

"Denenberg, Ray" <[log in to unmask]>

Reply-To:

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

Date:

Tue, 3 Jan 2017 15:42:58 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (1 lines)

Hi Jane -- 

 BIBRFRAME class AccessPolicy is really about policy, intending to reflect current cataloging rules,  rather than access conditions pertaining to specific scenarios.  I think that the use cases you mention are more along the lines of holdings and circulation. 

Even so, AccessPolicy is not an area that we plan to model, but rather, we define the class as a stub so that  descriptions can be supplied based on extensions defined by  external ontologies. There are some candidate ontologies that we are exploring.  

However, the area of holdings and circulation is possibly even more out of scope for BIBFRAME.  Similarly, there would need to be an external ontology developed by subject experts. There are existing protocols, but they would need to be turned into linked data ontologies.  We are also looking into this. 

Ray

> -----Original Message-----
> From: Bibliographic Framework Transition Initiative Forum
> [mailto:[log in to unmask]] On Behalf Of Jane Sandberg
> Sent: Friday, December 30, 2016 5:47 PM
> To: [log in to unmask]
> Subject: [BIBFRAME] How to describe complexities with bf:AccessPolicy?
> 
> Hello all,
> 
> I would like to learn more about the bf:AccessPolicy class. I didn't notice any
> specifics within the ontology about how these policies are to be modeled, and
> the only example I could find just hase the value "unrestricted" [1].  Is anybody
> looking into making this class a bit more robust, perhaps with their own
> ontology?
> 
> I am particularly interested in a use case in which a patron would know
> whether or not they could access a physical item, and how they would go about
> accessing it.  Take for example the BIBFRAME use case of Alex's mom who is
> searching for copies of the Phantom Tollbooth near her current location [2].
> This use case is overly simple: Alex's mom is probably not content just knowing
> that there are copies of the book nearby; she probably would be more
> interested in a query that returns nearby items that she could actually access.
> 
> This is complicated by the fact that Alex's mom could be looking for any of a
> number of different types of access:
> 
> 1) Checking out the item and taking it out of the library for a certain amout of
> time
> 
> 2) Checking out the item for use within the library (such as academic libraries'
> textbook collections, or keys to study rooms, etc.)
> 
> 3) Using the item within the library
> 
> 4) Getting the library item delivered to her (a service that some academic
> libraries offer to distance education students, some public libraries offer to
> homebound patrons, and some corporate libraries
> offer)
> 
> 5) Getting the item delivered to another library by a courier (which may take
> more time than Alex's mom would like)
> 
> 6) Placing a hold on the item to check out later (which is encouraged by some
> libraries, discouraged by others -- sometimes even with a small fee for holds)
> 
> Additionally, here are some complexities that Alex's mom would face if she
> lived in the county where I work:
> 
> 1) Our county has a consortium of municipal libraries, rather than a county-
> wide system.  So if Alex's mom didn't live in one of the cities that pays taxes
> toward its own municipal library, she would have to pay a non-resident fee
> before checking out any of those copies of the Phantom Tollbooth that are
> housed at those municipal libraries.
> 
> 2) The items might be checked out, damaged, or otherwise unavailable.
> 
> 3) Some libraries don't participate in the courier service.  So, depending on the
> library that holds the item, Alex's mom might have to visit the owning library in
> person.
> 
> 4) Each library has a different set of circulation and hold policies.
> 
> 5) Perhaps Alex's mom has a blocking fine at one of the libraries, or has been
> trespassed for violating some rule.  While the latter isn't particularly likely, I
> don't believe that any item has a truly "unrestricted" access policy.
> 
> So a much more useful query pattern for Alex's mom would include the
> following sorts of WHERE statements:
> * The bf:Item allows a type of access that interests Alex's mom
> * Alex's mom is actually allowed to use that type of access
> * Alex's mom can access that bf:Item in a reasonable amount of time
> 
> It would be very nice if bf:accessPolicy data could tell patrons what they could
> and could not access, and when they could access temporarily inaccessible or
> remote items.  Does anybody have any ideas about how that might work?
> 
> Thanks for your help!
> 
>    -Jane
> 
> [1] https://www.loc.gov/bibframe/docs/pdf/bf2-items-apr2016.pdf
> 
> [2] http://bibframe.org/documentation/bibframe-usecases/#holdings
> 
> --
> Jane Sandberg
> Electronic Resources Librarian
> Linn-Benton Community College
> [log in to unmask] / 541-917-4655
> Pronouns: she/her/hers or they/them/theirs

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

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