Sourcing Feature Basic Considerations
Jan 16, 2020 16:12:37 GMT -8
Post by Uncle Buddy on Jan 16, 2020 16:12:37 GMT -8
No one likes enforcementware but the person who writes it. I can see using something like that to design a nuclear power plant.
Genealogists often want to put a few people into their database on the fly while doing research, maybe to test a theory. It's not always appropriate to input all the people and events from a source right now. It should be done but not when the software designer makes you do it. Hobbies are supposed to be fun.
Treebard should have a new approach to sourcing. Sources should not have to be copy-pasted from entity to entity. That has to be thought out but there's no doubt an easier way to do it than the ones I've seen, and smartware is not the solution. The software should never make decisions for the user.
Sourcing has to be at the very core of a genieware but without being enforced. Now that I've gotten over the controllish notion of forcing users to input whole source forms so the software could create all the events at once, my way of making sources the heart of the program will be to separate assertions from conclusions and keep them separate.
On the person page there should be an events table where events can be input directly as conclusions. Each event row will have a sources button that has a readout on it for how many sources that event is based on. If you input a conclusion directly it has 0 sources. But you can also input assertions first instead of inputting conclusions directly. So if you have three birth assertions and combine them into one conclusion, only the conclusion will show on the events table, with a source button that reads "3". Click the button to open a dialog that shows you the three assertions from which you formed that conclusion.
Genealogists often want to put a few people into their database on the fly while doing research, maybe to test a theory. It's not always appropriate to input all the people and events from a source right now. It should be done but not when the software designer makes you do it. Hobbies are supposed to be fun.
Treebard should have a new approach to sourcing. Sources should not have to be copy-pasted from entity to entity. That has to be thought out but there's no doubt an easier way to do it than the ones I've seen, and smartware is not the solution. The software should never make decisions for the user.
Sourcing has to be at the very core of a genieware but without being enforced. Now that I've gotten over the controllish notion of forcing users to input whole source forms so the software could create all the events at once, my way of making sources the heart of the program will be to separate assertions from conclusions and keep them separate.
On the person page there should be an events table where events can be input directly as conclusions. Each event row will have a sources button that has a readout on it for how many sources that event is based on. If you input a conclusion directly it has 0 sources. But you can also input assertions first instead of inputting conclusions directly. So if you have three birth assertions and combine them into one conclusion, only the conclusion will show on the events table, with a source button that reads "3". Click the button to open a dialog that shows you the three assertions from which you formed that conclusion.