GEPS 018: Evidence style sources - Revision history

Romjerome: /* Entering source information */

2012-06-14T13:16:48Z

‎Entering source information

Romjerome: /* Further Reading */

2012-05-05T09:59:39Z

‎Further Reading

Romjerome: /* Further Reading */

2011-11-11T18:53:11Z

‎Further Reading

Romjerome: /* Further Reading */

2011-11-11T18:52:55Z

‎Further Reading

Romjerome: /* Further Reading */

2011-11-11T18:47:13Z

‎Further Reading

Romjerome: /* Further Reading */

2011-11-11T18:44:08Z

‎Further Reading

Romjerome: /* Further Reading */

2011-10-08T16:49:54Z

‎Further Reading

Daleathan: /* Bibliography Data Formats */

2011-08-31T22:48:46Z

‎Bibliography Data Formats

Jralls: /* Import/Export */ Add CSL and MODS

2011-08-31T15:29:10Z

‎Import/Export: Add CSL and MODS

Jralls: /* Proposed Interface changes */ Separate descriptions of interface, import/export, and storage

2011-08-16T18:16:49Z

‎Proposed Interface changes: Separate descriptions of interface, import/export, and storage

@@ Line 46: / Line 46: @@
 * Form based: The traditional keyboard data entry method. The fields can be fixed or flexible: The former is easier on the developers, the latter more helpful to users, especially if they are inexperienced.
-* Import: GRAMPS should be able to import (and export) source data from regular reference managers like [http://www.zotero.org Zotero], [http://pybliographer.org/ Pybliographer], and [http://www.bibtex.org BibTeX]. The Perl code in [http://www.scripps.edu/~cdputnam/software/bibutils/ BibUtils] could be adapted for to speed development.
+* Import: GRAMPS should be able to import (and export) source data from regular reference managers like [http://www.zotero.org Zotero], [http://pybliographer.org/ Pybliographer], and [http://www.bibtex.org BibTeX]. The Perl code in [http://sourceforge.net/p/bibutils/home/Bibutils/ BibUtils] could be adapted for to speed development.
 * Parsing: It's becoming more common for the large reference websites to provide a ready-made citation on the webpage along with the data or image being presented. (Google Books even offers to download it as a BibTeX file, but that's unfortunately not yet common). It would be very helpful if the user could just paste this citation into a block and GRAMPS took care of parsing it into the appropriate database fields. Experienced users might find typing into the parsing text-entry to be a faster way of inputting source data than using form based input.

@@ Line 32: / Line 32: @@
 * [http://recollection.zepheira.com/about/userguide/ Recollection project]
 * [http://sourcetemplates.org/ SourceTemplates.org]
-* [http://french-genealogy.typepad.com/genealogie/2010/11/a-sourcing-suggestion-insee-codes.html French case]
+* [http://french-genealogy.typepad.com/genealogie/2010/11/a-sourcing-suggestion-insee-codes.html French case] and [http://french-genealogy.typepad.com/genealogie/2012/05/sourcing-and-annotating-the-french-way.html sourcing and annotating].
 Citations and bibliography search engines:

@@ Line 35: / Line 35: @@
 Citations and bibliography search engines:
-** [http://www.francegenweb.org/~biblio/ GenWeb] using [http://wikindx.sourceforge.net/ WIKINDX3].
+* [http://www.francegenweb.org/~biblio/ GenWeb] using [http://wikindx.sourceforge.net/ WIKINDX3].
-** [http://catalog.loc.gov/ Library of Congress]
+* [http://catalog.loc.gov/ Library of Congress]
-** [http://gallica.bnf.fr/ Gallica]
+* [http://gallica.bnf.fr/ Gallica]
-** [http://catalogue.bnf.fr/jsp/recherchemots_simple.jsp?host=catalogue French national library]
+* [http://catalogue.bnf.fr/jsp/recherchemots_simple.jsp?host=catalogue French national library]
 =Workflow =

@@ Line 33: / Line 33: @@
 * [http://sourcetemplates.org/ SourceTemplates.org]
 * [http://french-genealogy.typepad.com/genealogie/2010/11/a-sourcing-suggestion-insee-codes.html French case]
-* Citations and bibliography search engines:
 ** [http://www.francegenweb.org/~biblio/ GenWeb] using [http://wikindx.sourceforge.net/ WIKINDX3].
 ** [http://catalog.loc.gov/ Library of Congress]

@@ Line 33: / Line 33: @@
 * [http://sourcetemplates.org/ SourceTemplates.org]
 * [http://french-genealogy.typepad.com/genealogie/2010/11/a-sourcing-suggestion-insee-codes.html French case]
-* Citations and bibliographical search engines:
+* Citations and bibliography search engines:
 ** [http://www.francegenweb.org/~biblio/ GenWeb] using [http://wikindx.sourceforge.net/ WIKINDX3].
 ** [http://catalog.loc.gov/ Library of Congress]

@@ Line 29: / Line 29: @@
 * [http://www.access.prov.vic.gov.au/public/PROVguides/PROVguide013/PROVguide013.jsp How to Cite Public Records]
 * [http://users.ecs.soton.ac.uk/harnad/citation.html The open citation (OpCit) linking project]
 * [http://www.thinkgenealogy.com/better-online-citations/ Better way to cite online sources]
 * [http://recollection.zepheira.com/about/userguide/ Recollection project]
 * [http://sourcetemplates.org/ SourceTemplates.org]
 =Workflow =

@@ Line 11: / Line 11: @@
 === Bibliography Data Formats ===
-* [www.bibtex.org BibTeX] has emerged as a common format (for interchange at least) among bibliography and reference management tools and offers a much richer set of available fields.
+* [http://www.bibtex.org BibTeX] has emerged as a common format (for interchange at least) among bibliography and reference management tools and offers a much richer set of available fields.
 * The U.S. Library of Congress has published the [http://www.loc.gov/standards/mods/ Metadata Object Description Schema], an XML schema for encoding library catalog data. That wouldn't be very interesting except that [http://www.scripps.edu/~cdputnam/software/bibutils/ BibUtils] uses it as an intermediate format for converting between a variety of bibliography file standards.
@@ Line 19: / Line 19: @@
 * Thompson-Reuters [http://en.wikipedia.org/wiki/EndNote EndNote] is easily the most popular commercial reference management program. It uses a proprietary file format which has nevertheless been reverse-engineered many times so that bibliographies can be easily exchanged between EndNotes and other reference managers.
 * Most of the major commercial genealogy programs use a proprietary relational schema for storage of citation data. These fall into two broad categories, binary (similar to GRAMPS's key/value schema, where a citation is composed of several records each having a key/value pair and the program's logic parses the keys to display the citation in the desired format), single-table (where a database tuple is defined which contains the maximum needed fields, each of which is assigned a value according to a parsing scheme in the programs logic), and multiple-table, where different citation types are stored in tables with tuple schema which reflect the requirements of each. As so often in programming, each has costs and benefits with respect to
 === Further Reading ===

@@ Line 95: / Line 95: @@
 == Import/Export ==
-Continued support of GEDCOM and GrampsXML is of course given. A [http://www.bibtex.org BibTex] import/export of source data would allow easy interchange with bibliography managers like [http://www.zotero.org Zotero] or [http://www.endnote.com EndNote].
+Continued support of GEDCOM and GrampsXML is of course given. A [http://www.bibtex.org BibTex], [http://www.loc.gov/standards/mods/ MODS], or [http://citationstyles.org/ Citation Style Language] import/export of source data would allow easy interchange with bibliography managers like [http://www.zotero.org Zotero] or [http://www.endnote.com EndNote].
 == Storage ==
 Several approaches are available for storage of this more elaborate source data:

@@ Line 89: / Line 89: @@
 =Proposed changes=
-==Proposed Interface changes==
+== User Interface ==
-How to store the fields? Attributes in the attribute tab of source?
+Instead of a one size fits all editor window, a template-controlled window (or wizard, but wizards get annoying for experienced users) would display a set of fields tailored to the selected source type.
 ==Proposed Report changes ==