Re: [gutvol-d] [BP] The Future of eBooks
----- Original Message ----- From: Alev Akman <aakman@csufresno.edu>
Maybe if the computer people stuck to "computering" and listened to how the library world does it? After all, the library sytems and conventions have been in place for a while.
Great! Answer my earlier question then. What fields should be mandatory for our <teiHeader> and which fields should be optional? ie, Author, title, Original publisher = mandatory. Optional? Author birth/death dates? Which printing of the original source we derived from? Others? I'm not a librarian. I need someone knowledgeable to answer these questions. Josh PS If we define good teiHeader information for each work, it becomes a much simpler task for Marcello's cataloging scripts to find all sorts of fun information for the reader.
On Wed, Nov 10, 2004 at 12:09:52PM -0500, Joshua Hutchinson wrote:
----- Original Message ----- From: Alev Akman <aakman@csufresno.edu>
Maybe if the computer people stuck to "computering" and listened to how the library world does it? After all, the library sytems and conventions have been in place for a while.
Great! Answer my earlier question then. What fields should be mandatory for our <teiHeader> and which fields should be optional?
(I don't know)
ie,
Author, title, Original publisher = mandatory.
Quick note: "Author" isn't the only term. The categories are: Author Illustrator Annotator Commentator Compiler Editor Illustrator Translator Unknown role These are the fields we use for copyright clearances & the online catalog. I think they match the MARC format too. They're used somewhat unevenly in the current eBook metadata field. -- Greg
Optional? Author birth/death dates? Which printing of the original source we derived from? Others?
I'm not a librarian. I need someone knowledgeable to answer these questions.
Josh
PS If we define good teiHeader information for each work, it becomes a much simpler task for Marcello's cataloging scripts to find all sorts of fun information for the reader.
Yes, this is the intent. Although the details are a little elusive right now, I think that including the authoritative catalog information in the XML file makes a lot of sense. The cataloging scripts are already ready for this. -- Greg
Joshua, I think the minimum mandatory fields should include: Author (including birth/death dates) Title (and/or Uniform Title) Subtitle (when it exists) Editor/Translator/Illustrator Date the book was published Physical properties of the "original print work" like number of pages, size of the book, illustrations, etc. Notes (Contents for collections, for example) Call numbers (LC/Dewey) Subjects Genre (that's where the Mystery, Historical Fiction, etc would come in) That's what I can think of now. Does the list help? Alev. At 09:09 AM 11/10/2004, you wrote:
----- Original Message ----- From: Alev Akman <aakman@csufresno.edu>
Maybe if the computer people stuck to "computering" and listened to how
the
library world does it? After all, the library sytems and conventions have been in place for a while.
Great! Answer my earlier question then. What fields should be mandatory for our <teiHeader> and which fields should be optional?
ie,
Author, title, Original publisher = mandatory.
Optional? Author birth/death dates? Which printing of the original source we derived from? Others?
I'm not a librarian. I need someone knowledgeable to answer these questions.
Josh
PS If we define good teiHeader information for each work, it becomes a much simpler task for Marcello's cataloging scripts to find all sorts of fun information for the reader. _______________________________________________ gutvol-d mailing list gutvol-d@lists.pglaf.org http://lists.pglaf.org/listinfo.cgi/gutvol-d
--- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.783 / Virus Database: 529 - Release Date: 10/25/2004
--- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.783 / Virus Database: 529 - Release Date: 10/25/2004
Joshua Hutchinson wrote:
What fields should be mandatory for our <teiHeader> and which fields should be optional?
Start with something like this: Note that the sourceDesc should always accurately describe the physical source. If you collect items from more than one phys. source all sources should be listed. Also if you split one physical source into multiple etexts, the source should appear in all etexs. Note the DP project number and the LoC Call Number. The LCCN should be given in the sourceDesc if it matches the physical source exactly. It should be given in the publicationStmt if it matches a different edition of the same work. Note: in the HTML file you'll have to enclose the teiHeader in comments and make sure you replace all occurences of -- inside the header with — You don't have to provide the <sourceDesc> and <profileDesc> stuff if you don't want to. I really just need the LCCN number and can pull the rest from the LoC database. An absolutely minimal header should look like: <teiHeader> <fileDesc> <publicationStmt> <idno type="dp-prj">DP Project Number goes here</idno> <idno type="lccn">Same work LCCN goes here.</idno> </publicationStmt> <sourceDesc> <biblStruct> <idno type="lccn">Only exact source LCCN goes here.</idno> </biblStruct> </sourceDesc> </fileDesc> </teiHeader> A full header should look like: <teiHeader> <fileDesc> <titleStmt> <title>Common sense</title> <author>Paine, Thomas (1737-1809)</author> </titleStmt> <publicationStmt> <publisher>Project Gutenberg</publisher> <idno type="dp-prj">DP Project Number goes here</idno> <idno type="lccn">Same work LCCN goes here.</idno> </publicationStmt> <editionStmt> <edition n='10'>First PG Edition</edition> </editionStmt> <notesStmt> <note><emph>Brief</emph> notes on the text.</note> </notesStmt> <sourceDesc> <biblStruct> <monogr> <editor>Foner, Philip S.</editor> <title>The collected writings of Thomas Paine</title> <imprint> <pubPlace>New York</pubPlace> <publisher>Citadel Press</publisher> <date value="1945-01">January 1945</date> </imprint> <extent>19 pp.</extent> </monogr> <idno type="lccn">Only exact source LCCN goes here.</idno> </biblStruct> </sourceDesc> </fileDesc> <encodingDesc> <classDecl> <taxonomy id="lcsh"> <bibl>Library of Congress Subject Headings</bibl> </taxonomy> <taxonomy id="lc"> <bibl>Library of Congress Classification</bibl> </taxonomy> <taxonomy id="lccn"> <bibl>Library of Congress Call Number</bibl> </taxonomy> <taxonomy id="dp-prj"> <bibl>Distributed Proofreaders Project Number</bibl> </taxonomy> </classDecl> </encodingDesc> <profileDesc> <creation> <date>Date text was created goes here: 1774</date> </creation> <langUsage> <language id="en">English.</language> </langUsage> <textClass> <keywords scheme="lcsh"> <list> <item>Political science</item> <item>United States — Politics and government — Revolution, 1775-1783</item> </list> </keywords> <classCode scheme="lc">JC 177</classCode> </textClass> </profileDesc> <revisionDesc> <change> <date value="2004-01">January 2004</date> <respStmt> <name>Joshua Hutchinson</name> <name>Tonya Allen</name> <name>Distributed Proofreaders Team</name> </respStmt> <item>Scanned and proofed it.</item> </change> </revisionDesc> </teiHeader> -- Marcello Perathoner webmaster@gutenberg.org
participants (4)
-
Alev Akman -
Greg Newby -
Joshua Hutchinson -
Marcello Perathoner