LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


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

CODE4LIB Home

CODE4LIB Home

CODE4LIB  January 2005

CODE4LIB January 2005

Subject:

Re: CODE4LIB Digest - 4 Jan 2005 to 5 Jan 2005 (#2005-2)

From:

"E. Llona" <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Thu, 6 Jan 2005 12:26:49 -0800

Content-Type:

TEXT/PLAIN

Parts/Attachments:

Parts/Attachments

TEXT/PLAIN (152 lines)

Thanks to all the input. I've always thought of XML as a transmission
tool, but more lately I've been thinking of it more for almost a
preservation mechanism for data, especially in terms of the institutional
repository movement. However, it seems ackward to deal with it in its
native form, as you also indicate, unless it's completely static and more
closely tied to the content. The projects I've been working have a fairly
structured format (such as gazetteer and census-type data), so it seems
like sticking with the database for storage might be the best way to go
for now.

Cheers,

Eileen

===================================================
Eileen Llona
International Studies Computer Services Librarian
Digital Initiatives, Suzzallo Library
University of Washington Seattle, WA 98195-2900

On Wed, 5 Jan 2005, Automatic digest processor wrote:

> There are 2 messages totalling 123 lines in this issue.
>
> Topics of the day:
>
>  1. advice about xml as storage
>  2. pymarc
>
> ----------------------------------------------------------------------
>
> Date:    Wed, 5 Jan 2005 10:31:00 -0500
> From:    Eric Lease Morgan <[log in to unmask]>
> Subject: Re: advice about xml as storage
>
> On Jan 4, 2005, at 5:56 PM, Ed Summers wrote:
>
>>> Can you offer advice on going/not going fully with XML for the
>>> storage mechanism?
>>
>> I tend to use XML as a transmission format: for serializing the
>> contents of an
>> database for consumption by a third party. Internally I use a
>> relational db as
>> a foundation for services I want to provide. So the rdbms serves as the
>> primary data source.
>
> I tend to agree with Ed, although this debate has been going on since
> the inception of XML. There is no one correct answer.
>
> I like using XML as the archival format for my text-based documents.
> This means I like to use TEI and XHTML as the basis of my writings and
> electronic texts. This technique allows me to separate my content from
> a specific application and/or operating system. I should be able to
> read these XML documents for years to come.
>
> Ironically, I use database applications to build the XML files. I use
> MySQL but stay away from any of their MySQL-isms such as the
> auto-increment feature. This allows me to use things like mysqldump to
> create a .sql files. Ideally I should be able to import these .sql
> files into other database applications. In reality, this is not always
> the case unless I tweak some of the SQL commands in the files, but
> since I'm dealing with plain text, this is not too difficult.
>
> Like Ed, I use databases to provide services against the data. More
> importantly, databases make it is easier to do things like global
> changes and update. It is more difficult to read bunches o' XML files,
> parse them, update accordingly, and write them again.
>
> In the XML world there are essentially two types of XML files:
> mixed-content files and not mixed content files. Good examples of
> mixed-content files are narrative texts. While still highly structured,
> narrative texts contains a large mixture of XML elements; there is
> relatively little repeating of elements in the same order. Non-mixed
> content have more pattern. These are more akin to data files with much
> more structure. In these cases the content is intended for statistical
> analysis. Average this. Sum that. Etc. Analysis of this data would be
> better done in a database application, not necessarily in an XML file
> through XSLT. Put another way, if your data is narrative in nature,
> like stories, consider more strongly saving your data as XML. On the
> other hand, if your data is more statistical in nature, think more
> strongly about using a database.
>
> In short, if you want to preserve your data, then use XML. If you want
> to do a lot of maintaining of the data (changing values, adding new
> content), then use databases. If you want to transform the data into
> other things like reports, printed documents, do analysis, then you
> will probably want to use a combination of both technologies.
>
> HTH.
>
> --
> Eric Lease Morgan
>
> ------------------------------
>
> Date:    Wed, 5 Jan 2005 17:21:25 -0600
> From:    Ed Summers <[log in to unmask]>
> Subject: pymarc
>
> Over the past few months I've been exploring python, and given my
> background with the perl module MARC::Record I set about writing pymarc
> which (I hope) extracts the essence of MARC::Record but provides a
> pythonic interface.
>
> The module works (ahem), and has a test suite, but I'm looking for feedback,
> so here's the URL:
>
>    http://www.python.org/pypi?:action=display&name=pymarc
>
> Here's a couple of examples from the docs:
>
> 1. Reading a batch of records and printing out the 245 subfield a:
>
>    from pymarc import MARCReader
>    reader = MARCReader( 'test/marc.dat' )
>    for record in reader:
>       print record['245']['a']
>
> 2. Print multiple fields from a record:
>
>    print record.fields( '600', '610', '650' )
>
> 3. Creating a record and writing it out to a file:
>
>    from pymarc import Record, Field
>    record = Record()
>    record.addField( \
>        Field( \
>            tag = '245',
>            indicators = ['0','1'],
>            subfields = [ \
>                'a', 'The pragmatic programmer : ',
>                'b', 'from journeyman to master /',
>                'c', 'Andrew Hunt, David Thomas.' ] ) )
>    out = file( 'file.dat', 'w' )
>    out.write( record.asMARC21() )
>
> There's a TODO list of things I'd like the module to do eventually. If
> anyone is interested in helping develop the library please let me know
> and I'll get you cvs (soon to be svn) access.
>
> Many thanks to Dan Chudnov for the python tips, advice and guidance which
> helped me get this far.
>
> //Ed
>
> ------------------------------
>
> End of CODE4LIB Digest - 4 Jan 2005 to 5 Jan 2005 (#2005-2)
> ***********************************************************
>

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

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
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager