PG Metadata

PG MetadataTop BoilerplateThis section explains the PG boilerplate that you must put at the top of your PG-RST file.It looks like this:.. -*- encoding: utf-8 -*- (1).. meta:: (2):PG.Id: 181:PG.Title: Very Short Title:PG.Released: 2010-11-25:PG.Rights: Public Domain:PG.Producer: Woody Guthrie:PG.Producer: Pete Seeger:PG.Producer: The Almanac Singers:PG.Credits: This file was produced from images stolen from the Louvre.:DC.Creator: Jane Austen:MARCREL.edt: Mark Twain:MARCREL.ill: Édouard Manet:DC.Title: Full Title Statement:DC.Language: en:DC.Language: fr:DC.Language: de:DC.Created: 1900:coverpage: images/cover.jpg===========Short Title (3)===========.. pgheader:: (4)Insert this line verbatim. It must be the first line in the text.6This tells the converter to use UTF-8 encoding and is also recognized by many editors.The metadata directive: see section below.This will be the first line of the generated files. It should say: “The Project Gutenberg Ebook of Title” or just “Title”. Use ’=’ above and below the title.This directive inserts the PG header as generated from the metadata.Metadata DirectiveThe metadata directive contains all data that is used to generate the PG header and the PG catalog entry.The scheme is the part before the dot.PG SchemeThe PG scheme holds data that is relevant to Project Gutenberg only.Fields In the PG SchemeNameContentsPG.IdThe ebook number.PG.ReleasedThe PG release date in YYYY-MM-DD format.PG.RightsEither ’Public Domain’ or ’Copyrighted’.PG.TitleA much shortened form of the title. Used in the PG boilerplate in the lines that say: “Start of this PG ebook …” and “End of this PG ebook …”.PG.ProducerA personal name or organization that helped produce this text. This field may appear more than once. Don’t put more than one name into one field. Repeat the field if necessary.PG.CreditsA line acknowledging the source of the images or other stuff.DC SchemeThis scheme holds standard Dublincore stuff and is used by many search engines and the PG cataloguing software.Fields In the DC SchemeNameContentsDC.CreatorAuthor. A personal name or organization that created the text. May appear more than once. Don’t put more than one name into one field. Repeat the field if necessary.DC.TitleThe full title statement as found on the book’s title page.DC.LanguageThe 2 or 3 letter code for all languages used for substantial portions of the text. May appear more than once. Don’t put more than one code into one field. Repeat the field if necessary. The languages listed here are indicative for the catalog and do not set the text language and hyphenation rules. Use the optionclasslanguage- for that.DC.CreatedThe year of original publication if known.MARCREL SchemeThis is used to record contributors to the text. All these fields may appear more than once. Don’t put more than one name into one field. Repeat the field if necessary.Fields In the MARCREL SchemeNameContentsMARCREL.edtEditorMARCREL.illIllustratorMARCREL.trlTranslatorMARCREL.*See thefull list of MARC relator codes.No SchemeSome fields are associated with none of the above schemes.Fields Without SchemeNameContentscoverpageA coverpage for those formats (eg. Kindle) that support a cover page. This image must be included in the upload but must not necessarily be put in the text flow.Bottom BoilerplateYou must put this at the very bottom of your PG-RST file... pgfooter:: (1)This directive inserts the PG footer and license.

Top BoilerplateThis section explains the PG boilerplate that you must put at the top of your PG-RST file.It looks like this:.. -*- encoding: utf-8 -*- (1).. meta:: (2):PG.Id: 181:PG.Title: Very Short Title:PG.Released: 2010-11-25:PG.Rights: Public Domain:PG.Producer: Woody Guthrie:PG.Producer: Pete Seeger:PG.Producer: The Almanac Singers:PG.Credits: This file was produced from images stolen from the Louvre.:DC.Creator: Jane Austen:MARCREL.edt: Mark Twain:MARCREL.ill: Édouard Manet:DC.Title: Full Title Statement:DC.Language: en:DC.Language: fr:DC.Language: de:DC.Created: 1900:coverpage: images/cover.jpg===========Short Title (3)===========.. pgheader:: (4)Insert this line verbatim. It must be the first line in the text.6This tells the converter to use UTF-8 encoding and is also recognized by many editors.The metadata directive: see section below.This will be the first line of the generated files. It should say: “The Project Gutenberg Ebook of Title” or just “Title”. Use ’=’ above and below the title.This directive inserts the PG header as generated from the metadata.

This section explains the PG boilerplate that you must put at the top of your PG-RST file.

It looks like this:

.. -*- encoding: utf-8 -*- (1).. meta:: (2):PG.Id: 181:PG.Title: Very Short Title:PG.Released: 2010-11-25:PG.Rights: Public Domain:PG.Producer: Woody Guthrie:PG.Producer: Pete Seeger:PG.Producer: The Almanac Singers:PG.Credits: This file was produced from images stolen from the Louvre.:DC.Creator: Jane Austen:MARCREL.edt: Mark Twain:MARCREL.ill: Édouard Manet:DC.Title: Full Title Statement:DC.Language: en:DC.Language: fr:DC.Language: de:DC.Created: 1900:coverpage: images/cover.jpg===========Short Title (3)===========.. pgheader:: (4)

Insert this line verbatim. It must be the first line in the text.6This tells the converter to use UTF-8 encoding and is also recognized by many editors.

The metadata directive: see section below.

This will be the first line of the generated files. It should say: “The Project Gutenberg Ebook of Title” or just “Title”. Use ’=’ above and below the title.

This directive inserts the PG header as generated from the metadata.

Metadata DirectiveThe metadata directive contains all data that is used to generate the PG header and the PG catalog entry.The scheme is the part before the dot.PG SchemeThe PG scheme holds data that is relevant to Project Gutenberg only.Fields In the PG SchemeNameContentsPG.IdThe ebook number.PG.ReleasedThe PG release date in YYYY-MM-DD format.PG.RightsEither ’Public Domain’ or ’Copyrighted’.PG.TitleA much shortened form of the title. Used in the PG boilerplate in the lines that say: “Start of this PG ebook …” and “End of this PG ebook …”.PG.ProducerA personal name or organization that helped produce this text. This field may appear more than once. Don’t put more than one name into one field. Repeat the field if necessary.PG.CreditsA line acknowledging the source of the images or other stuff.DC SchemeThis scheme holds standard Dublincore stuff and is used by many search engines and the PG cataloguing software.Fields In the DC SchemeNameContentsDC.CreatorAuthor. A personal name or organization that created the text. May appear more than once. Don’t put more than one name into one field. Repeat the field if necessary.DC.TitleThe full title statement as found on the book’s title page.DC.LanguageThe 2 or 3 letter code for all languages used for substantial portions of the text. May appear more than once. Don’t put more than one code into one field. Repeat the field if necessary. The languages listed here are indicative for the catalog and do not set the text language and hyphenation rules. Use the optionclasslanguage- for that.DC.CreatedThe year of original publication if known.MARCREL SchemeThis is used to record contributors to the text. All these fields may appear more than once. Don’t put more than one name into one field. Repeat the field if necessary.Fields In the MARCREL SchemeNameContentsMARCREL.edtEditorMARCREL.illIllustratorMARCREL.trlTranslatorMARCREL.*See thefull list of MARC relator codes.No SchemeSome fields are associated with none of the above schemes.Fields Without SchemeNameContentscoverpageA coverpage for those formats (eg. Kindle) that support a cover page. This image must be included in the upload but must not necessarily be put in the text flow.

The metadata directive contains all data that is used to generate the PG header and the PG catalog entry.

The scheme is the part before the dot.

PG SchemeThe PG scheme holds data that is relevant to Project Gutenberg only.Fields In the PG SchemeNameContentsPG.IdThe ebook number.PG.ReleasedThe PG release date in YYYY-MM-DD format.PG.RightsEither ’Public Domain’ or ’Copyrighted’.PG.TitleA much shortened form of the title. Used in the PG boilerplate in the lines that say: “Start of this PG ebook …” and “End of this PG ebook …”.PG.ProducerA personal name or organization that helped produce this text. This field may appear more than once. Don’t put more than one name into one field. Repeat the field if necessary.PG.CreditsA line acknowledging the source of the images or other stuff.

The PG scheme holds data that is relevant to Project Gutenberg only.

Name

Contents

PG.Id

The ebook number.

PG.Released

The PG release date in YYYY-MM-DD format.

PG.Rights

Either ’Public Domain’ or ’Copyrighted’.

PG.Title

A much shortened form of the title. Used in the PG boilerplate in the lines that say: “Start of this PG ebook …” and “End of this PG ebook …”.

PG.Producer

A personal name or organization that helped produce this text. This field may appear more than once. Don’t put more than one name into one field. Repeat the field if necessary.

PG.Credits

A line acknowledging the source of the images or other stuff.

DC SchemeThis scheme holds standard Dublincore stuff and is used by many search engines and the PG cataloguing software.Fields In the DC SchemeNameContentsDC.CreatorAuthor. A personal name or organization that created the text. May appear more than once. Don’t put more than one name into one field. Repeat the field if necessary.DC.TitleThe full title statement as found on the book’s title page.DC.LanguageThe 2 or 3 letter code for all languages used for substantial portions of the text. May appear more than once. Don’t put more than one code into one field. Repeat the field if necessary. The languages listed here are indicative for the catalog and do not set the text language and hyphenation rules. Use the optionclasslanguage- for that.DC.CreatedThe year of original publication if known.

This scheme holds standard Dublincore stuff and is used by many search engines and the PG cataloguing software.

Name

Contents

DC.Creator

Author. A personal name or organization that created the text. May appear more than once. Don’t put more than one name into one field. Repeat the field if necessary.

DC.Title

The full title statement as found on the book’s title page.

DC.Language

The 2 or 3 letter code for all languages used for substantial portions of the text. May appear more than once. Don’t put more than one code into one field. Repeat the field if necessary. The languages listed here are indicative for the catalog and do not set the text language and hyphenation rules. Use the optionclasslanguage- for that.

DC.Created

The year of original publication if known.

MARCREL SchemeThis is used to record contributors to the text. All these fields may appear more than once. Don’t put more than one name into one field. Repeat the field if necessary.Fields In the MARCREL SchemeNameContentsMARCREL.edtEditorMARCREL.illIllustratorMARCREL.trlTranslatorMARCREL.*See thefull list of MARC relator codes.

This is used to record contributors to the text. All these fields may appear more than once. Don’t put more than one name into one field. Repeat the field if necessary.

Name

Contents

MARCREL.edt

Editor

MARCREL.ill

Illustrator

MARCREL.trl

Translator

MARCREL.*

See thefull list of MARC relator codes.

No SchemeSome fields are associated with none of the above schemes.Fields Without SchemeNameContentscoverpageA coverpage for those formats (eg. Kindle) that support a cover page. This image must be included in the upload but must not necessarily be put in the text flow.

Some fields are associated with none of the above schemes.

Name

Contents

coverpage

A coverpage for those formats (eg. Kindle) that support a cover page. This image must be included in the upload but must not necessarily be put in the text flow.

Bottom BoilerplateYou must put this at the very bottom of your PG-RST file... pgfooter:: (1)This directive inserts the PG footer and license.

You must put this at the very bottom of your PG-RST file.

.. pgfooter:: (1)

This directive inserts the PG footer and license.

Back to Index Next