Difference between revisions of "User:BACbKA"
(dump out random thoughts that have piled up) |
|||
(4 intermediate revisions by one other user not shown) | |||
Line 5: | Line 5: | ||
* auto-translation of names, places, etc. - for reports and exports | * auto-translation of names, places, etc. - for reports and exports | ||
* reports & export should have more in common -- in filtering/selecting source set and output data | * reports & export should have more in common -- in filtering/selecting source set and output data | ||
+ | ** new action - filter, expose for cli? | ||
+ | ** see also bug #{{bug|1600}} and [[Filtered_Reports]] | ||
* what is the best practice for collaboration with other active researchers? Is there a tutorial? Should gramps collab with multisync @sf? or some DVCS? Obvious use cases: | * what is the best practice for collaboration with other active researchers? Is there a tutorial? Should gramps collab with multisync @sf? or some DVCS? Obvious use cases: | ||
# two (or more) people using GRAMPS. Each wants to be the master of his own DB and vet anything incoming. | # two (or more) people using GRAMPS. Each wants to be the master of his own DB and vet anything incoming. | ||
− | # make life easy for people taking periodic exports from gramps - can we send out only the stuff that changed? (yet another multisync sub-problem) | + | # make life easy for people taking periodic exports from gramps |
+ | |||
+ | This is a known hot issue, see [[How_you_can_help#Web_2.0]] | ||
+ | - can we send out only the stuff that changed? (yet another multisync sub-problem) | ||
+ | |||
+ | [[Category:User|B]] |
Revision as of 02:20, 20 October 2011
- merge familylines and relgraph good stuff into a common report
- auto-translation of names, places, etc. - for reports and exports
- reports & export should have more in common -- in filtering/selecting source set and output data
- new action - filter, expose for cli?
- see also bug #1600 and Filtered_Reports
- what is the best practice for collaboration with other active researchers? Is there a tutorial? Should gramps collab with multisync @sf? or some DVCS? Obvious use cases:
- two (or more) people using GRAMPS. Each wants to be the master of his own DB and vet anything incoming.
- make life easy for people taking periodic exports from gramps
This is a known hot issue, see How_you_can_help#Web_2.0 - can we send out only the stuff that changed? (yet another multisync sub-problem)