LISTSERV mailing list manager LISTSERV 16.0

Help for BIBFRAME Archives


BIBFRAME Archives

BIBFRAME Archives


[email protected]


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

BIBFRAME Home

BIBFRAME Home

BIBFRAME  September 2011

BIBFRAME September 2011

Subject:

Re: Description and Access functions in a post-MARC environment?

From:

Ed Jones <[log in to unmask]>

Reply-To:

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

Date:

Sun, 25 Sep 2011 09:32:56 -0700

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (102 lines)

If one determined that place of publication was worth the investment in time and resources necessary to render it useful for machine manipulation (e.g., how many works of fiction were published in London, Ontario, in 2007?), wouldn't it be more efficient to have a Publisher entity with associated places and dates? One might then, for example, select from among the places associated with a given publisher those that pertained to a given manifestation. If the places were themselves entities drawn from an outside geographical schema, all the better, if only for purposes of reliable manipulation and aggregation.
I remain unconvinced, however, that all this would be worth anywhere near the effort that would be needed to make it work. What exactly is a place of publication? The location of the editorial offices, of the corporate headquarters, of a post office box, or in some cases a deliberate deception? Is it the place in the imprint position on the title page or the different place identified as such on the verso? It quickly gets fuzzy, introducing a corresponding fuzziness into any analysis based on it. I am more comfortable regarding place of publication only as a physical mark helping to identify a given resource as the one sought.

Ed

Sent from my iPad

On Sep 25, 2011, at 3:04 AM, "Karen Coyle" <[log in to unmask]> wrote:

> What I haven't seen discussed here is the frequency with which this
> data is needed. When I post about making place of publication an
> actual place data element, I'm told there is rarely a need for it. How
> often is a precise comparison of title pages of essence? Is it worth
> making copies of all title pages for that number of instances? Does
> this apply to all works, or is there a niche where this has more use
> than, say, currently published trade books?
>
> What this comes down to is a need to look at all of our data practices
> and ask ourselves:
>
> - who needs this?
> - what is the context in which they need it?
> - how often is it used?
> - is there a more efficient way to provide this information?
> - is there a better way to achieve this goal?
>
> If I were being asked to create a new metadata scheme for Widgets,
> Inc., those are among the many questions I would ask of the providers
> and users of the information.
>
> One of the big difficulties that I see for this effort is that most of
> us come to the task with deeply ingrained practices and assumptions.
> We won't go very far forward if we can't re-visit all of these and
> decide what REALLY is needed today. This is why I recommend that there
> be some non-librarian IT folks consulted. As I said in a blog post, in
> fact that is exactly how MARC was developed - by an IT person who
> (fortunately!) was very good at listening to librarians.
>
> http://kcoyle.blogspot.com/2011/08/bibliographic-framework-transition.html
>
> kc
>
>
> Quoting Ed Jones <[log in to unmask]>:
>
>> Actually, I was thinking more of page images, trying to look at the
>> two kinds of data. I was viewing transcribed data as serving the
>> function of "Is this what you were looking for?" in which case, as
>> Robert points out, transcription is inexact, and a page image would
>> be more faithful. In a world where keyword searching is the default
>> mode for most of us, I see structured access points, etc.--the other
>> kind of data--as means of slicing and dicing the result set and
>> triggering related-entity searches. The whole text would indeed be
>> present in any contemporary e-text file--and even as imperfect OCR
>> in digitized older resources--to facilitate keyword searching, but I
>> wasn't thinking of any accompanying metadata. I wanted to try to
>> look at the question purely in terms of the two kinds of
>> data--three, if one includes the jumble of extracted text--and ask
>> whether, if the purpose of the transcribed sort is really to answer
>> this question-- "Is this what you were looking for?"--whether a page
>> image or two serves the purpose better.
>>
>> Ed
>>
>> Sent from my iPad
>>
>> On Sep 14, 2011, at 4:38 PM, "Mark Ehlert" <[log in to unmask]> wrote:
>>
>>> J. McRee Elrod <[log in to unmask]> wrote:
>>>> Ed Jones <[log in to unmask]> wrote:
>>>>
>>>>> Would transcription still be necessary if a title page (or analogous
>>>>> source for other types of resource) image were routinely included ...
>>>>
>>>> We include "thumbnails" of cover images for a major client (30,000
>>>> records so far). But they are images, and can not be keyword
>>>> searched.
>>>
>>> Ed's not referring to keyword searching an image with text. He's
>>> referring to, say, an ePub or PDF file of text (title page or whole
>>> work) within the coding of which is metadata that can be searched on
>>> or extracted and put into a database. You might be familiar with EXIF
>>> and image metadata, which is somewhat similar.
>>>
>>> --
>>> Mark K. Ehlert Minitex
>>> Coordinator University of Minnesota
>>> Bibliographic & Technical 15 Andersen Library
>>> Services (BATS) Unit 222 21st Avenue South
>>> Phone: 612-624-0805 Minneapolis, MN 55455-0439
>>> <http://www.minitex.umn.edu/>
>>
>
>
>
> --
> Karen Coyle
> [log in to unmask] http://kcoyle.net
> ph: 1-510-540-7596
> m: 1-510-435-8234
> skype: kcoylenet

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

June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
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