Hi Thayer,
well, donate to the project amounts basically to donating to me.
contact me in private, or have your institution do that, so we can
talk details. I do realize today it's the first of April, so
nicely played.
it's interesting the ODK Collect part. that was also my first
option. then, mostly because of the ODK Aggregator stuff there in
the middle, I preferred ghini.pocket. Ghini.pocket was born as a
quick tool for inventory review, it puts your collection in your
pocket, while ODK Collect is only for collecting data, as it
says. Orthography correction is a plus.
if you have code or documentation, it would be nice if you shared it. the GPL license allows and invites you to do so.
you haven't considered ghini.web? why not?
cheers,
Mario
--
You received this message because you are subscribed to the Google Groups "ghini/bauble" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bauble+un...@googlegroups.com.
To post to this group, send email to bau...@googlegroups.com.
Visit this group at https://groups.google.com/group/bauble.
For more options, visit https://groups.google.com/d/optout.
good morning Thayer,
I'll check the ODK Briefcase, but if you already have a working bridge to ghini, I could have a look and see how to integrate it into ghini.desktop.
about my email address, and ghini.web, there's some reference
material you possibly missed:
https://ghini.github.io/software/2018/02/22/new-family-picture.html
https://ghini.github.io/network/2018/03/24/cuba-poster.html
the pages of the above site, all contain the 'gh...@anche.no' email address, which is an alias to my private address. my name and email address is in the copyright statement of every source I significantly altered (all but three).thank you,
Mario
hi again Thayer,
I've looked a bit into your code, you say it yourself it's ugly and incomplete, but may I add this is not the best way to write stuff to a ghini database.
you are writing straight into the database, circumventing all of ghini's SQLAlchemy smartness.
while this is perfectly possible, this way you are missing the
'history' for all your operations. there might be other
contraindications, I'm not sure.
a better idea?
- convert the data into json, and have ghini import that.
https://github.com/Ghini/ghini.desktop/blob/ghini-1.0-dev/scripts/csv2json.py
this is mentioned in issue #127. I never found a garden interested in financing a better, more radical solution to this issue, so I never addressed it, I just adapted and re-adapted the same script, which in the meanwhile became more flexible, but remained a patchy work and never got a graphic interface within ghini.desktop.
in reality, ghini.desktop should import the data straight into the database, not go through json, and there should be a graphic interface to it. it's possibly a week work, maybe two, not more. the interface bits are already there, as you can see in the new "quick csv report", only available in ghini.desktop 3.1. we only have to use it the opposite way.
some reference material:
https://ghini.readthedocs.io/en/ghini-1.0-dev/imex.html
https://ghini.readthedocs.io/en/ghini-3.1-dev/imex.html
the documentation may be a bit behind the code, and the warning "this will destroy your data and may kill your cat" only applies to backup-restore (was called, up to ghini 1.0.88: "import csv files").
I didn't check your ODK Collect configurations yet, I'll let you know when I do that.
bests,
Mario