162
edits
Changes
From Gramps
→Entering source information: Input methods
==Entering source information ==
There are three broad alternatives for entering source data into a program, and GRAMPS should support all three:
* 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.
* 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.
=== Further Discussion of Form-based Input ===
When the end user cites a source for information, they would be prompted
with a window where they would select a main type and drill down
be in pop up menus for the user to select.
:''comment'': popup is not very user friendly, better would be a wizard button on the source editor, this lets you define the source, asks for fields, and shows the automatic citation markup based on the templates at the bottom while user adds fields. On Save, all this data is saved in the attributes as needed. To investigate if a new field is needed on source editor.
==Generating citation in reports ==
