Re: [CODE4LIB] Q.: software for vendor title list processing

[Annette Bailey]

Hey Ranti,

We do subscribe to Serials Solutions, but the title lists Godmar is
referring to are the title lists from the vendors that we get the content
from not the knowledge base that we then update.

Annette

On Thu, Oct 18, 2012 at 2:52 PM, Ranti Junus  wrote:

> Godmar,
>
> Does your library subscribe to Serials Solutions? If it does, I wonder
> if you could use the list from SerSols.
>
>
> ranti.
>
> On Tue, Oct 16, 2012 at 2:16 PM, Godmar Back  wrote:
> > Hi,
> >
> > at our library, there's an emerging need to process title lists from
> > vendors for various purposes, such as checking that the titles purchased
> > can be discovered via discovery system and/or OPAC. It appears that the
> > formats in which those lists are provided are non-uniform, as is the
> > process of obtaining them.
> >
> > For example, one vendor - let's call them "Expedition Scrolls" - provides
> > title lists for download to Excel, but which upon closer inspection turn
> > out to be HTML tables. They are encoded using an odd mixture of CP1250
> and
> > HTML entities. Other vendors use entirely different formats.
> >
> > My question is whether there are efforts, software, or anything related
> to
> > streamlining the acquisition and processing of vendor title lists in
> > software systems that aid in the collection development and maintenance
> > process. Any pointers would be appreciated.
> >
> >  - Godmar
>
>
>
> --
> Bulk mail.  Postage paid.
>

Re: [CODE4LIB] Q.: software for vendor title list processing

[Ranti Junus]

Godmar,

Does your library subscribe to Serials Solutions? If it does, I wonder
if you could use the list from SerSols.


ranti.

On Tue, Oct 16, 2012 at 2:16 PM, Godmar Back  wrote:
> Hi,
>
> at our library, there's an emerging need to process title lists from
> vendors for various purposes, such as checking that the titles purchased
> can be discovered via discovery system and/or OPAC. It appears that the
> formats in which those lists are provided are non-uniform, as is the
> process of obtaining them.
>
> For example, one vendor - let's call them "Expedition Scrolls" - provides
> title lists for download to Excel, but which upon closer inspection turn
> out to be HTML tables. They are encoded using an odd mixture of CP1250 and
> HTML entities. Other vendors use entirely different formats.
>
> My question is whether there are efforts, software, or anything related to
> streamlining the acquisition and processing of vendor title lists in
> software systems that aid in the collection development and maintenance
> process. Any pointers would be appreciated.
>
>  - Godmar



-- 
Bulk mail.  Postage paid.

Re: [CODE4LIB] Q.: software for vendor title list processing

[Owen Stephens]

> 
> This leads to three follow-up questions.
> 
> First, is there software to translate/normalize existing vendor lists from
> vendors that have not yet adopted either of these standards into these
> formats? I'm thinking of a collection of adapters or converters, perhaps.
> Each would likely constitute small effort, but there would be benefits from
> sharing development and maintenance.

Not that I'm aware of, but if I understand you then this is one of the tasks 
GoKB is undertaking in partnership with KB+ (the work I mentioned using Refine)

> 
> Second, if holdings lists were provided in, or converted to, for instance
> the KBART format, what software understands these formats to further
> process them? In other words, is there immediate bang for the buck of
> adopting these standards?

The KBART format was aimed at Link Resolver population - so I'd hope there was 
some immediate payback on this front, but I don't have any information on this

> 
> Third, unsurprisingly, these efforts arose in the managements of serials
> because holdings there change frequently depending on purchase agreements,
> etc. It is my understanding that eBooks are now posing similar collection
> management challenges. Are there separate normative efforts for eBooks or
> is it believed that efforts such as KBART/ONIX can encompass eBooks as well?
> 

KBART definitely has ambitions to encompass eBooks as well. There are already 
some hooks for this (e.g. 'first author' field), and the working group is 
looking at how ebooks will work I think

> - Godmar

Re: [CODE4LIB] Q.: software for vendor title list processing

[Godmar Back]

Thanks for everyone who replied to my question.

>From a brief examination, if I understand it correctly, KBART and ONIX
create normative standards for how holdings data should be represented,
which vendors (increasingly) follow.

This leads to three follow-up questions.

First, is there software to translate/normalize existing vendor lists from
vendors that have not yet adopted either of these standards into these
formats? I'm thinking of a collection of adapters or converters, perhaps.
Each would likely constitute small effort, but there would be benefits from
sharing development and maintenance.

Second, if holdings lists were provided in, or converted to, for instance
the KBART format, what software understands these formats to further
process them? In other words, is there immediate bang for the buck of
adopting these standards?

Third, unsurprisingly, these efforts arose in the managements of serials
because holdings there change frequently depending on purchase agreements,
etc. It is my understanding that eBooks are now posing similar collection
management challenges. Are there separate normative efforts for eBooks or
is it believed that efforts such as KBART/ONIX can encompass eBooks as well?

 - Godmar

Re: [CODE4LIB] Q.: software for vendor title list processing

[Owen Stephens]

There are things that could be improved about the KBART guidelines (and you've 
picked on one here I definitely agree with). 

There is an interest group mailing list which can be used for 
discussion/feedback http://www.niso.org/lists/kbart_interest/

I suspect that for both approaches at the moment the question of 
uptake/compliance is the bigger issue.

Owen

Owen Stephens
Owen Stephens Consulting
Web: http://www.ostephens.com
Email: o...@ostephens.com
Telephone: 0121 288 6936

On 17 Oct 2012, at 14:48, Jonathan Rochkind  wrote:

> I've always been a fan of ONIX for SOH, although never had the chance to use 
> it -- but the spec is written nicely, based on my experience with this stuff, 
> it actually accomplishes the goal of machine-readable statement of serial 
> holdings (theoretically useful for print or online holdings) well.
> 
> KBART, I have some concerns about, when it comes to holdings. Is there a 
> place to send feedback to KBART?  Just on a quick skim of the parts of 
> interest to me, I am filled with alarm at how much missing the point this is: 
>   " we recommend that the ISO 8601 date syntax should be used...  For 
> simplicity, '365D' will always be equivalent to one year, and '30D' will 
> always be equivalent to one month, even in leap years and months that do not 
> have 30 days."
> 
> Totally missing the point of ISO 8601 to allow/encourage this when 1Y and 1M 
> are available -- dealing with calendar dates is harder than one might naively 
> think, and by trying to 'improve' on ISO 8601 like this, you just create a 
> mess of ambiguous and difficult to deal with data.
> 
> On 10/17/2012 5:11 AM, Owen Stephens wrote:
>> Are there any examples of data in this format in the wild we can look at?
>> 
>> Also given KBART and ONIX for Serials Online Holdings have NISO involvement, 
>> is there any view on how these two activities complement each other?
>> 
>> Thanks,
>> 
>> Owen
>> 
>> Owen Stephens
>> Owen Stephens Consulting
>> Web: http://www.ostephens.com
>> Email: o...@ostephens.com
>> Telephone: 0121 288 6936
>> 
>> On 17 Oct 2012, at 09:47, Michael Hopwood  wrote:
>> 
>>> Hi Godmar,
>>> 
>>> There is also ONIX for Serials Online Holdings 
>>> (http://www.editeur.org/120/ONIX-SOH/). I'm copying in Tim Devenport who 
>>> might say more.
>>> 
>>> Best wishes,
>>> 
>>> Michael
>>> 
>>> -Original Message-
>>> From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of 
>>> Owen Stephens
>>> Sent: 16 October 2012 23:09
>>> To: CODE4LIB@LISTSERV.ND.EDU
>>> Subject: Re: [CODE4LIB] Q.: software for vendor title list processing
>>> 
>>> I'm working on the JISC KB+ project that Tom mentioned.
>>> 
>>> As part of the project we've been collating journal title lists from 
>>> various sources. We've been working with members of the KBART steering 
>>> group and have used KBART where possible, although we've been collecting 
>>> data not covered by KBART.
>>> 
>>> All the data we have at this level is published under a CC0 licence at 
>>> http://www.kbplus.ac.uk/kbplus/publicExport - including a csv that uses the 
>>> KBART data elements. The focus so far has been on packages negotiated by 
>>> JISC in the UK - although in many cases the title lists may be the same as 
>>> are made available in other markets. We also include what we call 'Master 
>>> lists' which are an attempt to capture the complete list of titles and 
>>> coverage offered by a content provider. We'd very much welcome any feedback 
>>> on these exports, and of course be interested to know if anyone makes use 
>>> of them.
>>> 
>>> So far a lot of the work on collating/coverting/standardising the data has 
>>> been done by hand - which is clearly not ideal. In the next phase of the 
>>> project the KB+ project is going to work with the GoKB project 
>>> http://gokb.org - as part of this collaboration we are currently working on 
>>> ways of streamlining the data processing from publisher files or other 
>>> sources, to standardised data. While we are still working on how this is 
>>> going to be implemented, we are currently investigating the possibility of 
>>> using Google/Open Refine to capture and re-run sets of rules across data 
>>> sets from specific sources. We should be making progress on this in the 
>>> next couple of months.
>>> 
>>> Ho

Re: [CODE4LIB] Q.: software for vendor title list processing

[Jonathan Rochkind]

I've always been a fan of ONIX for SOH, although never had the chance to 
use it -- but the spec is written nicely, based on my experience with 
this stuff, it actually accomplishes the goal of machine-readable 
statement of serial holdings (theoretically useful for print or online 
holdings) well.


KBART, I have some concerns about, when it comes to holdings. Is there a 
place to send feedback to KBART?  Just on a quick skim of the parts of 
interest to me, I am filled with alarm at how much missing the point 
this is:   " we recommend that the ISO 8601 date syntax should be 
used...  For simplicity, '365D' will always be equivalent to one year, 
and '30D' will always be equivalent to one month, even in leap years and 
months that do not have 30 days."


Totally missing the point of ISO 8601 to allow/encourage this when 1Y 
and 1M are available -- dealing with calendar dates is harder than one 
might naively think, and by trying to 'improve' on ISO 8601 like this, 
you just create a mess of ambiguous and difficult to deal with data.


On 10/17/2012 5:11 AM, Owen Stephens wrote:

Are there any examples of data in this format in the wild we can look at?

Also given KBART and ONIX for Serials Online Holdings have NISO involvement, is 
there any view on how these two activities complement each other?

Thanks,

Owen

Owen Stephens
Owen Stephens Consulting
Web: http://www.ostephens.com
Email: o...@ostephens.com
Telephone: 0121 288 6936

On 17 Oct 2012, at 09:47, Michael Hopwood  wrote:


Hi Godmar,

There is also ONIX for Serials Online Holdings 
(http://www.editeur.org/120/ONIX-SOH/). I'm copying in Tim Devenport who might 
say more.

Best wishes,

Michael

-Original Message-
From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Owen 
Stephens
Sent: 16 October 2012 23:09
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] Q.: software for vendor title list processing

I'm working on the JISC KB+ project that Tom mentioned.

As part of the project we've been collating journal title lists from various 
sources. We've been working with members of the KBART steering group and have 
used KBART where possible, although we've been collecting data not covered by 
KBART.

All the data we have at this level is published under a CC0 licence at 
http://www.kbplus.ac.uk/kbplus/publicExport - including a csv that uses the 
KBART data elements. The focus so far has been on packages negotiated by JISC 
in the UK - although in many cases the title lists may be the same as are made 
available in other markets. We also include what we call 'Master lists' which 
are an attempt to capture the complete list of titles and coverage offered by a 
content provider. We'd very much welcome any feedback on these exports, and of 
course be interested to know if anyone makes use of them.

So far a lot of the work on collating/coverting/standardising the data has been 
done by hand - which is clearly not ideal. In the next phase of the project the 
KB+ project is going to work with the GoKB project http://gokb.org - as part of 
this collaboration we are currently working on ways of streamlining the data 
processing from publisher files or other sources, to standardised data. While 
we are still working on how this is going to be implemented, we are currently 
investigating the possibility of using Google/Open Refine to capture and re-run 
sets of rules across data sets from specific sources. We should be making 
progress on this in the next couple of months.

Hope that's helpful

Owen

Owen Stephens
Owen Stephens Consulting
Web: http://www.ostephens.com
Email: o...@ostephens.com
Telephone: 0121 288 6936

On 16 Oct 2012, at 20:23, Tom Pasley  wrote:


You might also be interested in the work at http://www.kbplus.ac.uk .
The site is up at the moment, but I can't reach it for some reason...
they have a public export page which you might want to know about
http://www.kbplus.ac.uk/kbplus/publicExport

Tom

On Wed, Oct 17, 2012 at 8:12 AM, Jonathan Rochkind  wrote:


I think KBART is such an effort.  As with most library standards
groups, there may not be online documentation of their most recent
efforts or successes, but: http://www.uksg.org/kbart

http://www.uksg.org/kbart/s5/**guidelines/data_format<http://www.uksg
.org/kbart/s5/guidelines/data_format>



On 10/16/2012 2:16 PM, Godmar Back wrote:


Hi,

at our library, there's an emerging need to process title lists from
vendors for various purposes, such as checking that the titles
purchased can be discovered via discovery system and/or OPAC. It
appears that the formats in which those lists are provided are
non-uniform, as is the process of obtaining them.

For example, one vendor - let's call them "Expedition Scrolls" -
provides title lists for download to Excel, but which upon closer
inspection turn out to be HTML tables. They are encoded using

Re: [CODE4LIB] Q.: software for vendor title list processing

[Owen Stephens]

Are there any examples of data in this format in the wild we can look at?

Also given KBART and ONIX for Serials Online Holdings have NISO involvement, is 
there any view on how these two activities complement each other?

Thanks,

Owen

Owen Stephens
Owen Stephens Consulting
Web: http://www.ostephens.com
Email: o...@ostephens.com
Telephone: 0121 288 6936

On 17 Oct 2012, at 09:47, Michael Hopwood  wrote:

> Hi Godmar,
> 
> There is also ONIX for Serials Online Holdings 
> (http://www.editeur.org/120/ONIX-SOH/). I'm copying in Tim Devenport who 
> might say more.
> 
> Best wishes,
> 
> Michael
> 
> -Original Message-
> From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Owen 
> Stephens
> Sent: 16 October 2012 23:09
> To: CODE4LIB@LISTSERV.ND.EDU
> Subject: Re: [CODE4LIB] Q.: software for vendor title list processing
> 
> I'm working on the JISC KB+ project that Tom mentioned.
> 
> As part of the project we've been collating journal title lists from various 
> sources. We've been working with members of the KBART steering group and have 
> used KBART where possible, although we've been collecting data not covered by 
> KBART.
> 
> All the data we have at this level is published under a CC0 licence at 
> http://www.kbplus.ac.uk/kbplus/publicExport - including a csv that uses the 
> KBART data elements. The focus so far has been on packages negotiated by JISC 
> in the UK - although in many cases the title lists may be the same as are 
> made available in other markets. We also include what we call 'Master lists' 
> which are an attempt to capture the complete list of titles and coverage 
> offered by a content provider. We'd very much welcome any feedback on these 
> exports, and of course be interested to know if anyone makes use of them.
> 
> So far a lot of the work on collating/coverting/standardising the data has 
> been done by hand - which is clearly not ideal. In the next phase of the 
> project the KB+ project is going to work with the GoKB project 
> http://gokb.org - as part of this collaboration we are currently working on 
> ways of streamlining the data processing from publisher files or other 
> sources, to standardised data. While we are still working on how this is 
> going to be implemented, we are currently investigating the possibility of 
> using Google/Open Refine to capture and re-run sets of rules across data sets 
> from specific sources. We should be making progress on this in the next 
> couple of months.
> 
> Hope that's helpful
> 
> Owen
> 
> Owen Stephens
> Owen Stephens Consulting
> Web: http://www.ostephens.com
> Email: o...@ostephens.com
> Telephone: 0121 288 6936
> 
> On 16 Oct 2012, at 20:23, Tom Pasley  wrote:
> 
>> You might also be interested in the work at http://www.kbplus.ac.uk . 
>> The site is up at the moment, but I can't reach it for some reason... 
>> they have a public export page which you might want to know about 
>> http://www.kbplus.ac.uk/kbplus/publicExport
>> 
>> Tom
>> 
>> On Wed, Oct 17, 2012 at 8:12 AM, Jonathan Rochkind  wrote:
>> 
>>> I think KBART is such an effort.  As with most library standards 
>>> groups, there may not be online documentation of their most recent 
>>> efforts or successes, but: http://www.uksg.org/kbart
>>> 
>>> http://www.uksg.org/kbart/s5/**guidelines/data_format<http://www.uksg
>>> .org/kbart/s5/guidelines/data_format>
>>> 
>>> 
>>> 
>>> On 10/16/2012 2:16 PM, Godmar Back wrote:
>>> 
>>>> Hi,
>>>> 
>>>> at our library, there's an emerging need to process title lists from 
>>>> vendors for various purposes, such as checking that the titles 
>>>> purchased can be discovered via discovery system and/or OPAC. It 
>>>> appears that the formats in which those lists are provided are 
>>>> non-uniform, as is the process of obtaining them.
>>>> 
>>>> For example, one vendor - let's call them "Expedition Scrolls" - 
>>>> provides title lists for download to Excel, but which upon closer 
>>>> inspection turn out to be HTML tables. They are encoded using an odd 
>>>> mixture of CP1250 and HTML entities. Other vendors use entirely different 
>>>> formats.
>>>> 
>>>> My question is whether there are efforts, software, or anything 
>>>> related to streamlining the acquisition and processing of vendor 
>>>> title lists in software systems that aid in the collection 
>>>> development and maintenance process. Any pointers would be appreciated.
>>>> 
>>>> - Godmar
>>>> 
>>>> 
>>>> 

[CODE4LIB] FW: [CODE4LIB] Q.: software for vendor title list processing

[Michael Hopwood]

Hi Godmar,

There is also ONIX for Serials Online Holdings 
(http://www.editeur.org/120/ONIX-SOH/). I'm copying in Tim Devenport who might 
say more.

Best wishes,

Michael

-Original Message-
From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Owen 
Stephens
Sent: 16 October 2012 23:09
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] Q.: software for vendor title list processing

I'm working on the JISC KB+ project that Tom mentioned.

As part of the project we've been collating journal title lists from various 
sources. We've been working with members of the KBART steering group and have 
used KBART where possible, although we've been collecting data not covered by 
KBART.

All the data we have at this level is published under a CC0 licence at 
http://www.kbplus.ac.uk/kbplus/publicExport - including a csv that uses the 
KBART data elements. The focus so far has been on packages negotiated by JISC 
in the UK - although in many cases the title lists may be the same as are made 
available in other markets. We also include what we call 'Master lists' which 
are an attempt to capture the complete list of titles and coverage offered by a 
content provider. We'd very much welcome any feedback on these exports, and of 
course be interested to know if anyone makes use of them.

So far a lot of the work on collating/coverting/standardising the data has been 
done by hand - which is clearly not ideal. In the next phase of the project the 
KB+ project is going to work with the GoKB project http://gokb.org - as part of 
this collaboration we are currently working on ways of streamlining the data 
processing from publisher files or other sources, to standardised data. While 
we are still working on how this is going to be implemented, we are currently 
investigating the possibility of using Google/Open Refine to capture and re-run 
sets of rules across data sets from specific sources. We should be making 
progress on this in the next couple of months.

Hope that's helpful

Owen

Owen Stephens
Owen Stephens Consulting
Web: http://www.ostephens.com
Email: o...@ostephens.com
Telephone: 0121 288 6936

On 16 Oct 2012, at 20:23, Tom Pasley  wrote:

> You might also be interested in the work at http://www.kbplus.ac.uk . 
> The site is up at the moment, but I can't reach it for some reason... 
> they have a public export page which you might want to know about 
> http://www.kbplus.ac.uk/kbplus/publicExport
> 
> Tom
> 
> On Wed, Oct 17, 2012 at 8:12 AM, Jonathan Rochkind  wrote:
> 
>> I think KBART is such an effort.  As with most library standards 
>> groups, there may not be online documentation of their most recent 
>> efforts or successes, but: http://www.uksg.org/kbart
>> 
>> http://www.uksg.org/kbart/s5/**guidelines/data_format<http://www.uksg
>> .org/kbart/s5/guidelines/data_format>
>> 
>> 
>> 
>> On 10/16/2012 2:16 PM, Godmar Back wrote:
>> 
>>> Hi,
>>> 
>>> at our library, there's an emerging need to process title lists from 
>>> vendors for various purposes, such as checking that the titles 
>>> purchased can be discovered via discovery system and/or OPAC. It 
>>> appears that the formats in which those lists are provided are 
>>> non-uniform, as is the process of obtaining them.
>>> 
>>> For example, one vendor - let's call them "Expedition Scrolls" - 
>>> provides title lists for download to Excel, but which upon closer 
>>> inspection turn out to be HTML tables. They are encoded using an odd 
>>> mixture of CP1250 and HTML entities. Other vendors use entirely different 
>>> formats.
>>> 
>>> My question is whether there are efforts, software, or anything 
>>> related to streamlining the acquisition and processing of vendor 
>>> title lists in software systems that aid in the collection 
>>> development and maintenance process. Any pointers would be appreciated.
>>> 
>>>  - Godmar
>>> 
>>> 
>>> 

Re: [CODE4LIB] Q.: software for vendor title list processing

[Owen Stephens]

I'm working on the JISC KB+ project that Tom mentioned.

As part of the project we've been collating journal title lists from various 
sources. We've been working with members of the KBART steering group and have 
used KBART where possible, although we've been collecting data not covered by 
KBART.

All the data we have at this level is published under a CC0 licence at 
http://www.kbplus.ac.uk/kbplus/publicExport - including a csv that uses the 
KBART data elements. The focus so far has been on packages negotiated by JISC 
in the UK - although in many cases the title lists may be the same as are made 
available in other markets. We also include what we call 'Master lists' which 
are an attempt to capture the complete list of titles and coverage offered by a 
content provider. We'd very much welcome any feedback on these exports, and of 
course be interested to know if anyone makes use of them.

So far a lot of the work on collating/coverting/standardising the data has been 
done by hand - which is clearly not ideal. In the next phase of the project the 
KB+ project is going to work with the GoKB project http://gokb.org - as part of 
this collaboration we are currently working on ways of streamlining the data 
processing from publisher files or other sources, to standardised data. While 
we are still working on how this is going to be implemented, we are currently 
investigating the possibility of using Google/Open Refine to capture and re-run 
sets of rules across data sets from specific sources. We should be making 
progress on this in the next couple of months.

Hope that's helpful

Owen

Owen Stephens
Owen Stephens Consulting
Web: http://www.ostephens.com
Email: o...@ostephens.com
Telephone: 0121 288 6936

On 16 Oct 2012, at 20:23, Tom Pasley  wrote:

> You might also be interested in the work at http://www.kbplus.ac.uk . The
> site is up at the moment, but I can't reach it for some reason... they have
> a public export page which you might want to know about
> http://www.kbplus.ac.uk/kbplus/publicExport
> 
> Tom
> 
> On Wed, Oct 17, 2012 at 8:12 AM, Jonathan Rochkind  wrote:
> 
>> I think KBART is such an effort.  As with most library standards groups,
>> there may not be online documentation of their most recent efforts or
>> successes, but: http://www.uksg.org/kbart
>> 
>> http://www.uksg.org/kbart/s5/**guidelines/data_format
>> 
>> 
>> 
>> On 10/16/2012 2:16 PM, Godmar Back wrote:
>> 
>>> Hi,
>>> 
>>> at our library, there's an emerging need to process title lists from
>>> vendors for various purposes, such as checking that the titles purchased
>>> can be discovered via discovery system and/or OPAC. It appears that the
>>> formats in which those lists are provided are non-uniform, as is the
>>> process of obtaining them.
>>> 
>>> For example, one vendor - let's call them "Expedition Scrolls" - provides
>>> title lists for download to Excel, but which upon closer inspection turn
>>> out to be HTML tables. They are encoded using an odd mixture of CP1250 and
>>> HTML entities. Other vendors use entirely different formats.
>>> 
>>> My question is whether there are efforts, software, or anything related to
>>> streamlining the acquisition and processing of vendor title lists in
>>> software systems that aid in the collection development and maintenance
>>> process. Any pointers would be appreciated.
>>> 
>>>  - Godmar
>>> 
>>> 
>>> 

Re: [CODE4LIB] Q.: software for vendor title list processing

[Tom Pasley]

You might also be interested in the work at http://www.kbplus.ac.uk . The
site is up at the moment, but I can't reach it for some reason... they have
a public export page which you might want to know about
http://www.kbplus.ac.uk/kbplus/publicExport

Tom

On Wed, Oct 17, 2012 at 8:12 AM, Jonathan Rochkind  wrote:

> I think KBART is such an effort.  As with most library standards groups,
> there may not be online documentation of their most recent efforts or
> successes, but: http://www.uksg.org/kbart
>
> http://www.uksg.org/kbart/s5/**guidelines/data_format
>
>
>
> On 10/16/2012 2:16 PM, Godmar Back wrote:
>
>> Hi,
>>
>> at our library, there's an emerging need to process title lists from
>> vendors for various purposes, such as checking that the titles purchased
>> can be discovered via discovery system and/or OPAC. It appears that the
>> formats in which those lists are provided are non-uniform, as is the
>> process of obtaining them.
>>
>> For example, one vendor - let's call them "Expedition Scrolls" - provides
>> title lists for download to Excel, but which upon closer inspection turn
>> out to be HTML tables. They are encoded using an odd mixture of CP1250 and
>> HTML entities. Other vendors use entirely different formats.
>>
>> My question is whether there are efforts, software, or anything related to
>> streamlining the acquisition and processing of vendor title lists in
>> software systems that aid in the collection development and maintenance
>> process. Any pointers would be appreciated.
>>
>>   - Godmar
>>
>>
>>

Re: [CODE4LIB] Q.: software for vendor title list processing

[Jonathan Rochkind]

I think KBART is such an effort.  As with most library standards groups, 
there may not be online documentation of their most recent efforts or 
successes, but: http://www.uksg.org/kbart


http://www.uksg.org/kbart/s5/guidelines/data_format


On 10/16/2012 2:16 PM, Godmar Back wrote:

Hi,

at our library, there's an emerging need to process title lists from
vendors for various purposes, such as checking that the titles purchased
can be discovered via discovery system and/or OPAC. It appears that the
formats in which those lists are provided are non-uniform, as is the
process of obtaining them.

For example, one vendor - let's call them "Expedition Scrolls" - provides
title lists for download to Excel, but which upon closer inspection turn
out to be HTML tables. They are encoded using an odd mixture of CP1250 and
HTML entities. Other vendors use entirely different formats.

My question is whether there are efforts, software, or anything related to
streamlining the acquisition and processing of vendor title lists in
software systems that aid in the collection development and maintenance
process. Any pointers would be appreciated.

  - Godmar

[CODE4LIB] Q.: software for vendor title list processing

[Godmar Back]

Hi,

at our library, there's an emerging need to process title lists from
vendors for various purposes, such as checking that the titles purchased
can be discovered via discovery system and/or OPAC. It appears that the
formats in which those lists are provided are non-uniform, as is the
process of obtaining them.

For example, one vendor - let's call them "Expedition Scrolls" - provides
title lists for download to Excel, but which upon closer inspection turn
out to be HTML tables. They are encoded using an odd mixture of CP1250 and
HTML entities. Other vendors use entirely different formats.

My question is whether there are efforts, software, or anything related to
streamlining the acquisition and processing of vendor title lists in
software systems that aid in the collection development and maintenance
process. Any pointers would be appreciated.

 - Godmar