Difference between revisions of "GEPS 024: Natural transcription of Records"
m (moved GEPS 023: Certificates to GEPS 024: Certificates: There was already a 23) |
m (→See also) |
||
(4 intermediate revisions by 2 users not shown) | |||
Line 31: | Line 31: | ||
* Gramps' FamilySearch API will perhaps have the ability to connect and download an entire census sheet. Consider creating the Certificate from the downloaded definition. | * Gramps' FamilySearch API will perhaps have the ability to connect and download an entire census sheet. Consider creating the Certificate from the downloaded definition. | ||
+ | |||
+ | = See also = | ||
+ | * [[GEPS_012:_Ecosystem_definition#Certificates|Ecosystem definition]] | ||
+ | * [[Citations]] | ||
+ | * [[DataEntryGramplet]], [[Census_Addons|Census addon]], [[ImportGramplet]]. | ||
+ | * {{bug|5552}}: Handle sources/records Indexing | ||
+ | |||
+ | [[Category:GEPS|C]] |
Revision as of 17:35, 14 October 2012
A Gramps Certificate is defined to be a method for creating and storing genealogical information from a document. For example, one might create a Census Certificate that would allow users to enter data straight from a Census sheet. The associated data would be stored in a well-defined location in the database, and in exported file formats.
Needs
- A manner to create, and edit over time, a certificate definition
- See Gramps Census XML format
- A way to view the certificate
- A way to map certificate fields onto database items
- A way to recreate the document from the database (see Gramps Census Report)
One important aspect to consider is the manner to store the Certificate data in a well-defined, GEDCOM-exportable manner.
Current Census Limitations
Things needed to bring the Census work up to this level of integration:
- If you change the way a certificate is defined, we need a way to change the data. For example, changing a column name disassociates all of the information in the database.
- How to handle translations?
- Code should be able to add items such as sources to the database
- Items lose their ordering
Example Workflow
- Find a census sheet that you would like to enter data from
- Select it. That will add the necessary Source records in the database, if they do not exist
- That brings up a data entry view
- Enter data
- Save data, which stores the columns in the appropriate place, and creates any needed events, etc.
Other Connections
- Gramps' FamilySearch API will perhaps have the ability to connect and download an entire census sheet. Consider creating the Certificate from the downloaded definition.
See also
- Ecosystem definition
- Citations
- DataEntryGramplet, Census addon, ImportGramplet.
- 5552: Handle sources/records Indexing