|
このページはEtoJ逐語翻訳フィルタによって翻訳生成されました。 |
You may find that the database 含むd in LibreOffice or OpenOffice delights you as much as it has me. This page tries to help you use it.
Remember that Libre Office or Open Office, 含むing the database module, is 解放する／自由な. Don't let that fool you, though. Big organizations, 政治の and 非軍事の, have 可決する・採択するd it as their 基準 office 控訴... and saving million$, but still Getting The 職業 Done. And making things 平易な for 使用者s on different 壇・綱領・公約s... Linux, Mac, Windows all spoken here!
There's more about Libre Office in the main 索引 to this 構成要素. Adabas? 星／主役にする Office? 古代の history.
This page is "browser friendly". Make your browser window as wide as you want it. The text will flow nicely for you. It is easier to read in a 狭くする window. With most browsers, 圧力（をかける）ing 加える, minus or 無 while the 支配（する）／統制する 重要な (ctrl) is held 負かす／撃墜する will change the texts size. (大きくする, 減ずる, 回復する to default, それぞれ.) (This is fully explained, and there are more tips, at my 力／強力にする Browsing page.)
Page contents © TK Boyd, Sheepdog ソフトウェア, 6/10- 3/25.
This essay will 調査する how Libre Office can help family history 熱中している人s looking into their genealogy.
It is not meant to 提案する a finished system for actual use. If you want a database for genealogy work, I 示唆する you 支払う／賃金 for a professionally invented, 精製するd and supported 道具.
It will, I hope, help you see things about Good Database Design, and about 記録，記録的な／記録する keeping for family history 熟考する／考慮するs.
It will, I hope, serve as a starting point, from which Libre Office programmers more 技術d that I can 延長する the story.
Beware: You may find yourself disappointed, or even annoyed when you get to the end of this essay. It takes you a long way に向かって a 完全にする family tree database... but not all the way. I hope to 延長する it in 予定 course... but it's not all there yet!
More by luck than design, I started 記録，記録的な／記録するing my family history 研究 成果／努力s with "Kith and 肉親，親類", from Spansoft. The fact that it was and is "try before you buy", i.e. shareware, was a major factor 主要な to my 採択 of the program.
This is "try before you buy"... and a SENSIBLE 裁判，公判, by the way. In June 2010, the ソフトウェア was 申し込む／申し出d for &続けざまに猛撃する;38 for Kith and 肉親，親類 WITH Tree Draw. (For the extra you 支払う／賃金, I'd certainly buy the Tree Draw while you're at it!). The proce 3/2021: &続けざまに猛撃する;35 the pair! (^_^) (Or &続けざまに猛撃する;30 for Kith And 肉親，親類 on its own.)
If "my" design for 記録，記録的な／記録するing genealogical 研究 results looks very like Spansoft's, I believe it is because it is "the obvious" way to do it. Ford doesn't get upset when Mercedes 解放（する）s a car with four wheels. 陳謝s to Spansoft if they think I "stolen" a "proprietary" idea... but isn't there a 説 that imitation is the most sincere form of compliment?
You will not build a "copy" of Kith and 肉親，親類 with the help of this essay. That's why, if you really want to 記録，記録的な／記録する family history data, that I recommend that you buy a "proper" answer, be it Kith and 肉親，親類 or another. This essay is meant to build your database design and 開発 技術s, and show you some of the features of Libre Office's Base RDBMS.
Whatever 一括 you 選ぶ for: Be sure it 申し込む／申し出s "輸出（する） to GEDCOM". This is the "lingua franca" for genealogists, and 未来-proofs your work.
Also be sure to keep meticulous 記録，記録的な／記録するs of where your "facts" come from.
Family tree 研究 is a nice example of how fitting the real world into the finicky world of the computer 要求するs some careful thought.
With ANY database, you need to ask yourself: What （警察などへの）密告，告訴（状） do I have? How should I 蓄える／店 it? What do I want to get 支援する from the database?
Except for trivial database 仕事s, there are 代案／選択肢 ways to do a given 職業. The 代案／選択肢 ways will each have strengths and 証拠不十分s... and the skilful database developer knows how to go 負かす／撃墜する the road which leads to the answer with the best 妥協s between the different 代案／選択肢 answers.
見本 Data For Our Discussion
So that we have something to "get our teeth into", here is some real family history. If you can tell me more about any of these people, by the way, they are of 利益／興味 to me.
We'll come 支援する to the computer 味方する of things in a moment. First we need to talk about things all genealogists have always struggled with... even in the days before computers.
1) Family History data is unreliable and "fuzzy". 20 years ago I "knew" of two Boyds in London, dob 1/1/1820 and 2/2/1818, それぞれ. 指名するd James and Henry. Five years ago, I leaned that my "two Boyds" were one person: James Henry Boyd, b. 1/1/1818. (Okay, so I made that example up... but that sort of thing happens!)
2) It is 必須の to have a system in place which 許すs you to find things in all the 公式文書，認めるs you have made about people you are (or may be) 関係のある to. For example...
What told you that Ebenezer's wife was Ruth? Family bible? 国勢（人口）調査? What?
... or ...
Percy Seville Boyd? Where did you see that 指名する before? Ah! Percival Boyd. (Say "Percy Seville" quickly) Heck. Not another Percy Seville after all.
If you can 正確に 持つ／拘留する what you know about your family in your 長，率いる, you don't know much about them yet!
If you （問題を）取り上げる family history 追跡（する）ing, you should try from the start to be rigorous about keeping 正確な 記録，記録的な／記録するs not just what you know (Uncle John's wife was Mary), but how you know it... They were at your birthday party? You've got a copy of their marriage 証明書 from the 国家の 登録（する）? (And if you do: Can you lay your 手渡すs on it?)
Try to keep these 必要物／必要条件s in mind as we now turn to "注ぐing everything" into an Libre Office database.
The 創立／基礎 of any database is its （米）棚上げする／（英）提議するs.
The 支配するs of 標準的にする／正常にするd （米）棚上げする／（英）提議する design take some mastering, but, even at my "journeyman" level, I fully embrace the value of those 支配するs and that 肉親，親類d of （米）棚上げする／（英）提議する, even though I can't yet make them do all I would wish. But! I have some experience of 支払う／賃金ing the price for bending the 支配するs, and I've not yet 設立する a 事例／患者 where the 支配するs have really made it impossible to do something I 手配中の，お尋ね者 to do. Wikipedia has a useful article on 標準的にする／正常にするd （米）棚上げする／（英）提議する design.
標準的にする／正常にするd （米）棚上げする／（英）提議するs won't have duplicated data, unless you count 入ること／参加（者）s in （米）棚上げする／（英）提議する "A" of values in （米）棚上げする／（英）提議する "B" when those 入ること／参加（者）s are 単に there to create links 記録，記録的な／記録するs between the two （米）棚上げする／（英）提議するs. Good （米）棚上げする／（英）提議する design often helps 確実にする that your （米）棚上げする／（英）提議するs don't have unnecessary "empty spaces". (That's one of the things that makes it "good"!)
If the （米）棚上げする／（英）提議するs in a database each relate to a real "thing" in the real world, they are often 平易な to "get 権利".
Enough theory! On to our example.
Remember: We are not trying to make a database which would have everything a genealogist would want... For instance, I won't 含む a way to 記録，記録的な／記録する dates of marriage into the database. There WILL be a way to enter dates of birth or Christening. From that, I 推定する／予想する you to be able to see how the database MIGHT be 育てる／巣立つd out to a more 完全にする 製品... but I would still advise you not to do this; buy a "proper" family tree 記録，記録的な／記録するing 控訴.
You can download a .obd とじ込み／提出する called FDB009 with all that this tutorial discusses already 始める，決める up, and with data... but if you build it with me, as 始める，決める out in the 構成要素 below, you'll understand everything better.
First （米）棚上げする／（英）提議する: "People": The obvious place to start is not やむを得ず a bad place!
Almost all of our （米）棚上げする／（英）提議するs, for this 演習, will have "boring" 最初の／主要な 重要な fields. There is no end to the clever things you can... and often should... do when designing the 最初の／主要な 重要な for a （米）棚上げする／（英）提議する. But we won't 調査する ideas in that area in this essay. In every （米）棚上げする／（英）提議する, there will be a 最初の／主要な 重要な field. It will be the first field in the （米）棚上げする／（英）提議する. Usually, it will be an "autovalue" (自動車-incrementing) integer. It will have a simple 指名する like PeoID which stands for "a PEOple's 記録，記録的な／記録する ID, for the people （米）棚上げする／（英）提議する." (You might 簡単に call this field "ID" in all of the （米）棚上げする／（英）提議するs. The computer would 対処する, but I will give each a different 指名する, ending in ID, to make talking about them 平易な.)
So.... first field, of the "People" （米）棚上げする／（英）提議する, the first （米）棚上げする／（英）提議する we will build: PeoID, data type: integer.
Next two fields: Date of birth or Christening/ Date of Death. "DOBC", "DOD". Data type: Date (Don't get me started on all the 問題／発行するs that little simplification entails! Every time we talk about a date in a database... any database... we are on the brink of a discussion which could fill several 調書をとる／予約するs. In 新規加入, the さまざまな dates needed in a family history database have a slew of extra, genealogy-明確な／細部 複雑化s. For now, we'll leave it at that, apart from 追加するing that any dates in the 見本 data are to be considered as かもしれない approximate. (If you can help me with, say, the real world Robert Andrew Boyd, but "your" Robert Andrew died in 1867, don't 結論する that he's a different Robert Andrew from the one of 利益／興味.)
Next two fields: Surname, given 指名するs. "Snam", "Gnam". Text. Length 20. So... 法案 Clinton's wife would be 記録，記録的な／記録するd as Snam= Rodham, Gnam= Hillary. It may surprise you that we don't need to put the married 指名する in the People （米）棚上げする／（英）提議する. If we NEEDED it, we'd have to make a field, but, for many Western Europeans at least, think about it: Half the time (the men), there wouldn't be a need to enter their surname in two places. And in any 事例／患者, many people marry more than once. Having fields like "first married 指名する", "second married 指名する", etc. is BAD IDEA. How many such fields would you need to 供給する to each 記録，記録的な／記録する, anyway? You'll see that we get around all these problems やめる neatly in just a little while.
Like dates, 指名するs are the source of many, many woes... which again, I am funking for now.
The last (!) field we need for the "People" （米）棚上げする／（英）提議する is a "Child of" field. We'll call it "ChdOf", and it will be of type integer. More on this later. (初めは, I was going to call it "CldOf", but if you can 避ける ones and "ells" in field 指名するs, you won't later have problems because someone reads, say, and ell (l) as a one (1). (Of course, 避けるing "ohs" and 無s is another good thing to do, but I failed to come up with a （疑いを）晴らす 指名する without the "oh".)
One （米）棚上げする／（英）提議する 負かす／撃墜する!
"Fams" is going to be the 指名する for the next （米）棚上げする／（英）提議する. The 指名する is short for "families", which won't in every 事例／患者 mean what we 一般に mean by "family". I わびる if you find that 縮めるing of the 指名する distasteful, but for some of the things we may 結局 want to do, short 指名するs help us.
How's your history? Did you know (I didn't) that Richard III of England (r.1483-1485), had two children by Katherine Haute, who was not his wife? (The children were John of Gloucester and Katherine, who married William Herbert, 2nd Earl of Pembroke.)
For our 目的s, Richard and Katherine Haute will be considered "a family".
By the way, Wikipedia gets 十分な 示すs for temperance. When I asked it for "famous bastards", Wikipedia asked if I meant "famous last words"? But I digress.
However 複雑にするd the 事件／事情／状勢s of men and women become, I think I'm 安全な in setting up the database upon a 前提 that each child will have 正確に／まさに one (生物学の) father and 正確に／まさに one (生物学の) mother. While much of the world is messy, and not "computer friendly", some things are "tidier". (Surrogacy raises some 利益／興味ing 問題／発行するs, though!)
I will "digress" again for a moment... but this time with more in mind that just lightening the トン of all this.
I once ran the database for a school, in which the 詳細（に述べる）s of our pupils were held. One boy made a difficulty for me by having two dates of birth! (He （機の）カム from a country ours was at 半端物s with. He flew from home on one パスポート, birthdate "A", changed 計画（する）s and パスポートs in a 中立の country, and arrived with us on his second パスポート, birthdate "B". "When first we practise to deceive...", and all that.
Anyway! 支援する to work!
The "Fams" （米）棚上げする／（英）提議する needs only three fields:
As "Fath" and "Moth" 持つ／拘留する PeoID values, you can, I hope, see that these fields must also be of type integer. (But those fields will not be 自動車-incrementing, i.e. not "autovalue".)
Now, in a "real" family tree database we would certainly have a "Date of Marriage" field. But as we have enough date fields in our example database already, won't put the "date of marriage" field in.
See something 冷静な／正味の? If someone doesn't marry, there's no wasted space. On the other 手渡す, if you want Henry VIII in the database, it can 融通する his 6 weddings without breaking a sweat. If we have 詳細（に述べる）s of any children of Henry and women he wasn't married to, they can go in too!
We'll start with some real people, about whom I would like to know more, John and Sarah Boyd, of London, England. They had, at least, two sons: Robert Andrew and William, dates of birth or Christening 1815 and 1817 それぞれ; died 1869 and 1883. (All of the （警察などへの）密告，告訴（状） you will be given in the text is in the more 伝統的に drawn family tree that comes with this essay. There may be some （警察などへの）密告，告訴（状） in the database at the end of the 演習 which has come from the 伝統的な tree, but didn't get について言及するd in the essay.)
現実に, we should 始める，決める up 関係s (using that 称する，呼ぶ／期間／用語 in the database sense) before we start entering data. We せねばならない create a 関係 between People.PeoId and Fams.Fath, and we せねばならない create a 関係 between People.PeoId and Fams.Moth. Do that if you know how; struggle with it for Extra Credit, if you don't!
(There's more on 関係s and joins in a short(er) page I've done talking about these important 概念s in general 条件. They are not the same thing, but the differences 絶えず blur in my mind, and I hope to help you fight that problem.
First we enter John and Sarah in the People （米）棚上げする／（英）提議する. If you are, as I was, entering them as the first 記録，記録的な／記録するs, they will 結局最後にはーなる with PeoID 0 and 1. (Computers count from 無.)
The numbers in the PeoID field don't "mean" anything... the are only there so that...
a) Every 記録，記録的な／記録する in the （米）棚上げする／（英）提議する has a unique identifier, and
b) We have a way to say "that one", concisely, if we want to 明示する a 選び出す／独身 記録，記録的な／記録する, which, also as it happens, 明示するs a 選び出す／独身 person.
For John and Sarah, and indeed for many people and families, we do not, will not know everything. We won't fill in every field for every 記録，記録的な／記録する.
The computer, as I tried to explain above, will automatically 問題／発行する a number for the PeoID field. (Every 記録，記録的な／記録する must have an 入ること／参加（者） in this field.)
Other than that, for John and Sarah, we can only make a total of three 入ること／参加（者）s in the People （米）棚上げする／（英）提議する: Snam and Gnam for John, Gnam for Sarah.
A fancier family history database might let us fill in a guess or approximation for their dates of birth and death, and give us a way to 記録，記録的な／記録する the basis of our guess, and an 指示，表示する物 of 限界s on it. I'd say, for instance, that as they had a child in 1815, they were probably both born before 1802 (!)... but that is a 詳細（に述べる）. In this essay, I am trying to paint the 幅の広い picture.
Now that we have values in the PeoID field of the People （米）棚上げする／（英）提議する (that, by the way, can be 表明するd with "Now that we have People.PeoID values"), we can create a 記録，記録的な／記録する in the Families （米）棚上げする／（英）提議する, to 可能にする entering Robert Andrew Boyd's data, 完全にする with the （警察などへの）密告，告訴（状） about who his parents were.
"Fams" （米）棚上げする／（英）提議する
FamID Fath Moth <-- Fields
0 0 1 <-- Values, first 記録，記録的な／記録する.That "says": The family we are calling "無" consists of the man with "無" in his People.PeoID field, and the woman with "one" in her People.PeoID field.
Now go 支援する to the People （米）棚上げする／（英）提議する, and enter the 詳細（に述べる）s for Robert Andrew and William:
PeoID DOBC DOD Snam Gnam ChdOf
2 1815 1869 Boyd Robert Andrew 0
3 1817 1883 Boyd William 0(Remember: The PeoID numbers are 問題／発行するd by the computer. If I'd entered William, and then Robert, the PeoID for William would have been "2".)
Remember I said that I would NOT get bogged 負かす／撃墜する in "dates" data 詳細（に述べる）s? All dates in this デモ database will be January 1st of the year the real date was in. This 許すs us to use "Date" 判型 fields, but saves us 確かな discussions.
The default 陳列する，発揮する 判型 for a date uses just two digits for the year. 始める，決める the 陳列する，発揮する 判型 to show 4 digits. (Yes, I'm "cheating", "存在 bad" at this point, and working 直接／まっすぐに with the （米）棚上げする／（英）提議するs. YOU of course would Be Good, and 始める，決める up forms, and interact with the （米）棚上げする／（英）提議するs through the forms. But you don't have this, and other, essays to 令状! I've created forms for you for the major （米）棚上げする／（英）提議するs.)
That's (almost!) it! With so little, you can do a 広大な／多数の／重要な 取引，協定! Marvel at the elegance! Don't worry about the difficulties you may be imagining. They could arise from things like trying to 簡単に remember that the number for John and Sarah's 連絡事務 is "0". The computer will help us with things like that, but it can only do so because we have things 適切に, in a good, computer friendly, way. Computer friendly in its 内部のs. We can make the 外部のs human friendly.
I'll take you through 追加するing some more 指名するs to the database, just to be sure. Do think as you are doing it... does what you are doing Make Sense? (If not, 人物／姿／数字 out what you're 行方不明の... or 令状 to me and "complain") You have to enter things in the order given, or the PeoIDs and FamIDs won't be as in this essay, and I won't be able to tell you what to put in other places where you enter them by 手渡す later.
追加する Robert Andrew's wife Mary to the People （米）棚上げする／（英）提議する...
PeoID Snam Gnam
4 Lunham Mary
Make an 入ること／参加（者） for her and Robert Andrew in the Fams （米）棚上げする／（英）提議する...
FamID Fath Moth
1 2 4
... and now we can enter John James....
PeoID DOBC Snam Gnam
5 1847 Boyd John James
Got it? That's "all" there is it... to the extent that we've developed the database so far. In the downloadable とじ込み／提出する, you will find the 残り／休憩（する） of the people shown in the "伝統的な" family tree, above. They were all entered as above. Nothing new or fancy was needed.
So far, we have a bad database for 記録，記録的な／記録するing the results of 研究 into family history. We can 記録，記録的な／記録する people and their 生物学の 関係s... important... but we have not made any 準備／条項 for 記録，記録的な／記録するing how we know what we know.
The first step in my own 追求（する），探索（する） to "tame" the 大混乱 of all the bits and pieces I've collected about my own family, and about people who might be part of my tree was to decide that everything, somehow or other, would be 減ずるd to individual 文書s, usually just 選び出す／独身 sheet of paper. And each would have a unique "指名する".
That approach brought several advantages. For one thing, I can keep a copy of all my source 文書s, and if anything happens to my "prime" copy, my work isn't lost.
いつかs the "source 文書" will 単に be a 記録，記録的な／記録する of where something can be 設立する, for instance it may say "See 一時期／支部 5 of (such and such a 調書をとる／予約する". Other times, my source 文書 is a copy... my prime, 最終的な copy... of something else, e.g. the family tree in the 前線 of the family bible.
A quick word about the IDs I use on my actual source 文書s. These 詳細（に述べる）s may help you define a good system for your needs. Not because you will 正確に／まさに 可決する・採択する my system, but because by 熟考する／考慮するing it you can see some of the 罠（にかける）s and some of the answers.
On the 文書 itself, I might 令状 something like "fhs402c03a". The "fhs" stands for "Family History Source (文書). For the 目的s of a database, within the database we will be able to infer the "fhs" from the 状況, so we won't need to (and indeed shouldn't) type it in over and over again.
The "4" is 現在の for many, many of my 文書s... which is an argument for putting it at the 権利 手渡す end of the identifier, but I have it at the "wrong" end as the best choice between two 始める，決めるs of evils. It comes from "A4", the European 任命 of paper that is about the size of what people in the US call "letter" sized. いつかs there's a "5" in that position. There's a "5" when the 文書 is a piece of "A5" sized paper (half a sheet of A4). Those are the only two values I use in that position at the moment, but the system can be 拡大するd as the need arises. That would happen if I 設立する myself collecting source 構成要素 in other physical 判型s. Who knows? I may one day get an A2 printer, and will have large sheets of paper to catalog and 蓄える／店. 公式文書，認める that by having this character in the code, I can 蓄える／店 all the A4 sized things together, all the A5 sized things together, etc, and (in theory!) never have any trouble in laying my 手渡すs on a particular 文書. (Within their size 部類s, I 簡単に 蓄える／店 them "in order", によれば their IDs.)
The next two characters are always digits. They come from the year the 文書 was 割り当てるd its ID. Happily, I only started this after 1999, and I don't 推定する／予想する it to be needed beyond 2099, so the "02" in the example says that this 文書 received its ID in 2002.
The month a 文書 ID was created is 示すd with a 選び出す／独身 character. 1,2,3...9 for Jan, February, March .. September. For October, November, December, I use "a" "b", "c" それぞれ. It seems a little 半端物 at first, but there are 重要な advantages , and you soon get used to it. The 文書 in the example got its ID... "fhs402c03a"... in December.
The next two... always two... characters are always digits, and come from the day of the month the 文書 was given the ID. Put a 主要な 無 in 前線 of 1,2,3...9. The 文書 in the example got its ID on December ("c") third ("03").
By the way... throughout, I use lower 事例／患者 letters. They're easier for the 注目する，もくろむ to distinguish, having ascenders and descenders within the data, and I find the 転換 重要な a nuisance, not 存在 a 技術d typist. As I won't have to type them as often, and for the （警察などへの）密告，告訴（状） which can be passed by the 明言する／公表する of the letters, I use mixed 事例／患者 for （米）棚上げする／（英）提議する and field 指名するs, e.g. "People", and "PeoID".
The last character is used sequentially. The first 文書 given an ID on a given day has an "a" at the 権利 手渡す end, the next is given the "b", then "c", "d"... etc.
WHY NOT.... just use "1" as the whole 指名する for the first 文書, "2" for the next, "3" for the next... and so on??
井戸／弁護士席... you can. But the my system means that you only have to remember what work you have done TODAY to know what the next ID should be! いつかs I am collecting data in 状況／情勢s where 接近ing my main 記録，記録的な／記録するs isn't 平易な.
===
So. We have a pile of 文書s, and a way to give each of them an ID. For the 目的s of FDB009, the database that comes with this tutorial, the database we are "building" here, we are not going to use the ID 計画／陰謀 I have just explained. We're 単に going to use a serially 問題／発行するd number, and preface the ID numbers with "sd" to stand for "source 文書". For the sake of our その上の discussions, we'll pretend that we have the に引き続いて 文書s....
That will do for now. Of course, in a real family history 記録，記録的な／記録する keeping 状況／情勢, there would be many, many 文書s.
This one will be called "Sources". It will be a catalog of the source 文書s, the sort of 文書 we have just been discussing.
"Sources" will have three fields:
SouID: The 最初の／主要な 重要な for the （米）棚上げする／（英）提議する, but NOT an integer, NOT 割り当てるd to 記録，記録的な／記録するs automatically by the computer. The SouID field in FDB009 is of type "Text", 直す／買収する，八百長をするd length of 5 (use 6 i f you want the "sd" and you thing you'll go over 1000 source 文書s!), and 持つ／拘留するs things like "sd001". As with the "fhs" I use in my actual data 記録，記録的な／記録するing, the "sd" could be left out of the 記録，記録的な／記録するs in FDB009. I 港／避難所't done that in the machine readable copy of FDB009 which is 利用できる for download, though, just to make SouIDs 平易な to 認める anywhere they arise, inside the computer or outside, during our consideration of doing family tree and history 記録，記録的な／記録するing.
The second field in Sources will be called "T", for "type", and will 持つ／拘留する a 選び出す／独身 character. (Hence the telegraphic 指名する for the field... we don't want to have to make a column for that data 4 times wider than it needs to be, just so we can 陳列する，発揮する the column 長，率いるing!)
* If Sources.t="b", then the source 文書 is a birth or baptismal 証明書. (In the real world, you'd want to give them different codes.)
* If Sources.t="s" the 文書 is a marriage license, defining "Spouses".
* I reserved the "m" code for that most glorious of 部類s: "Miscellaneous". If you always give yourself a "m" code, you never have to "軍隊" something into a 部類 which isn't really 権利, a 部類 which is 単に "least bad".
Finally, the last field of "Sources" will be called "Desc", for description, and will be 始める，決める up to 持つ／拘留する a short string of text. While it will tempt you to "二塁打 enter" some data, as long as you 扱う／治療する Sources.Desc as just a 目録ing 援助（する）, you'll be okay. You'd probably put "Robert Andrew Boyd 1815" into the desc field for his birth 証明書... AND enter the same （警察などへの）密告，告訴（状） in his 記録，記録的な／記録する in the People （米）棚上げする／（英）提議する. You can, 現実に, skip the 入ること／参加（者） in the Sources （米）棚上げする／（英）提議する, if you wish to, for a birth 証明書. You'll know WHOSE birth 証明書 it is by other means, and you'll know that it is a birth 証明書 from the Sources.t 入ること／参加（者）. However, not every source 文書 will be so self obvious. The Letter from Aunt Rene, 説 in part, "visited John, his wife Sarah and boys Robert and William", is an example of something where the description might be 特に useful. And the system gives you something important along the way: A means of going 支援する, and checking the source, to see if it was 解釈する／通訳するd 井戸／弁護士席.
Here are our source 文書s again, this time with their "T" coding, 同様に.
If the work the database was covering was a 共同の 事業／計画（する） between several people, you would want a field in Sources to 設立する who had collected the data in that source 文書.
It may occur to you that some fields might usefully be made "入ること／参加（者） 要求するd" fields. While some 記録，記録的な／記録するs will be meaningless without data in 確かな fields, I tend not to 始める，決める the "入ること／参加（者） 要求するd" 旗. Overuse can make entering data tedious.
Remember when libraries had card catalogs? If so, 耐える with me for a moment....
Once upon a time, if you went to a library to borrow a copy of Ridley Pearson's 2010 調書をとる／予約する for young adults, The 学院, you went to the "card catalog". It was a 始める，決める of drawers filled with small cards, usually 3" x 5". There was a card for "Pearson, Ridley", and a card for "学院, The". And these cards were とじ込み／提出するd alphabetically. Each card held the other data, and also an 指示，表示する物 of where in the library the 調書をとる／予約する would be 設立する. You could find the "where is it" （警察などへの）密告，告訴（状） either from the "Pearson" card or from the "学院" card. The first Pearson card you looked at might not be the one you needed, but you would be の近くに to it.
Of course, all of this is usually done (and done 井戸／弁護士席) by computers today. The library computer database has a "調書をとる／予約するs" （米）棚上げする／（英）提議する, with fields for author, 肩書を与える and 場所, and forms which give rise to the results of searches for, say, "Pearson" or "学院".
So far, so good. What the old fashioned, cellulose based card catalog was good at was 取引，協定ing with exceptions. Suppose someone 手配中の，お尋ね者 anyone looking at either card to know that the 調書をとる／予約する had been given to the library by the author. 平易な! Just make a 公式文書，認める on each card. Computer systems are not nearly so 柔軟な, without extra work. You can't just "追加する" a 非，不，無-基準 "公式文書，認める" to just some cards. But I said not so 柔軟な without extra work. It is that "extra work" that I am going to 述べる now, in the 状況 of our family tree data 記録，記録的な／記録するing 事例／患者 熟考する／考慮する.
We're going to have one discussion but, arising from it, 追加する three new （米）棚上げする／（英）提議するs to the database.
===
In the course of our 研究, we will find out things about People, "Families" and the Sources we have 協議するd in our 研究... things that won't "fit" nicely into the fields we have 供給するd in our three （米）棚上げする／（英）提議するs, our （米）棚上げする／（英）提議するs for those （独立の）存在s.
No problem! We just create three new （米）棚上げする／（英）提議するs!! I've called them NotesP, NotesF and NotesS. It doesn't 支払う／賃金 to be imaginative when 取引，協定ing with computers, as the are unimaginative by nature.
Each （米）棚上げする／（英）提議する will have a 最初の／主要な 重要な field of the simple "meaningless" integer 肉親，親類d. I've called those fields "NpID", "NfID" and "NsID". And each 記録，記録的な／記録する will have second field called "公式文書，認める", of type "覚え書き". 覚え書き fields are 広大な／多数の／重要な for 注ぐing 半端物s and ends of text into... but have shortcomings in many other ways. While the database we are building for the 目的s of discussion only has this simple 準備／条項 for 公式文書，認めるs, a "real" family tree database might have 準備／条項 for two sorts of 公式文書，認めるs, long 公式文書，認めるs and short 公式文書，認めるs. The former would be 供給するd for as we have 供給するd for "公式文書，認めるs" in general, and the latter would be 類似の, but the "公式文書，認める" field would be of a simple "text" data type.
Have a look at some of the "公式文書，認めるs" in the 供給（する）d database.
Has a problem occurred to you? It is "How do we match 公式文書，認めるs up with the person, family or source 文書 they relate to?" Pretty important! Why not just use the ID of the person, etc, as the ID for the 公式文書，認める? You could... if...
There was only ever one 公式文書，認める per person, etc.
and...
You never 手配中の，お尋ね者 to "connect" a given 公式文書，認める to more than one person, etc.
The problem does have a 解答... three more （米）棚上げする／（英）提議するs! I've called them NotesPKey, NotesFKey and NotesSKey. I was going to do it as one （米）棚上げする／（英）提議する, but the difference between the 計画／陰謀s for the 最初の／主要な 重要なs of the Sources 記録，記録的な／記録するs, and those in the other （米）棚上げする／（英）提議するs got in the way of my "cunning 計画（する）". (There were other ways around the problem, but the "three （米）棚上げする／（英）提議するs" answer seemed best here. Just 追加するing a "this 公式文書，認める 適用するs to (id given) 記録，記録的な／記録する" field would have worked やめる 井戸／弁護士席... but it didn't 供給する for "大（公）使館員ing" a 選び出す／独身 公式文書，認める to 多重の 記録，記録的な／記録するs.)
The three （米）棚上げする／（英）提議するs are 類似の, and 類似の to the "Families" （米）棚上げする／（英）提議する you have already seen.
Each starts with an 自動車-incrementing integer, to give the 記録，記録的な／記録する a 最初の／主要な 重要な.
Then there are two more fields: One for the 公式文書，認める, and one for ID of the person, family or source 文書 it 取引，協定s with.
See the 見本 database for some instances of the NotesPKey, NotesFKey and NotesSKey in 活動／戦闘.
It may seem I've gone "（米）棚上げする／（英）提議する mad"... and there is one more to go... but by 効果的な use of （米）棚上げする／（英）提議するs you can bring yourself many advantages. Your database can be smaller. The data in it can have "正直さ", in other words things "fit together" 適切に.
We're going to build a way to see what source 文書s we have for any particular person or family. You might think we've already got this, but the NotesPKey, NotesFKey and NotesSKey （米）棚上げする／（英）提議するs 単に tell us what NOTES we have for any person, family or source 文書.
The （米）棚上げする／（英）提議する 指名する, "ReDocPF", needs a little explanation. It is short for "RElating source DOCuments to People or Families (and 副／悪徳行為 versa)". This 職業 could, by the way, be done with two （米）棚上げする／（英）提議するs. It might be more obvious to do it that way, but what I've done shows you a "新たな展開", a variation on what we did before... and it just "feels 権利". Why have two （米）棚上げする／（英）提議するs, when a 職業 can be done with one?
The first field 持つ／拘留するs, as usual, a simple meaningless, autovalue integer to give each 記録，記録的な／記録する a 最初の／主要な 重要な value. The field is called "ReID", for "RElationships （米）棚上げする／（英）提議する ID"
追加する the に引き続いて fields after that:
How do we use these fields? What goes in them?
Remember our hypothetical copy of Robert Andrew Boyd's birth 証明書? 解任する that we gave it "sd001" for an ID for this discussion, eschewing the more コンビナート／複合体 "fhs402c03a"- type ID code I use in my real world 事例／患者 of this sort of work.
That 文書 would give rise to the に引き続いて 記録，記録的な／記録する in ReDocPF
ReID SDID PFID PF
0 sd001 2 p
Hang in there! This may seem "impossible" and "stupid"... but we're nearly "at the 最高の，を越す of the mountain", where you will see a thing of wonder and beauty spread out beneath your feet!
The example just given 作品 like this....
The "0" for ReID "just happened". It is the value 割り当てるd to the 記録，記録的な／記録する "by the system".
For SDID, we put sd001 because that is the 文書 we want to enter into the database.
For PFID, we entered 2 because that is the id number for Robert Andrew Boyd (the 支配する of sd001) in the People （米）棚上げする／（英）提議する, i.e. his People.PeoID number.
For PF, we entered "p" to 示す that this 記録，記録的な／記録する 報告（する）／憶測s a Person who is at least a part of the 支配する 事柄 of sd001.
And that does it! At last! We now have a viable system for 持つ／拘留するing what we've 設立する about families history, and how we know the things we've discovered. We 港／避難所't done much (yet) to make it "使用者 friendly" (whew!), and I'll give another example 関係のある to ReDocPF in a moment, but we are DONE creating （米）棚上げする／（英）提議するs!!
Here's another ReDocPF example. Think 支援する to sd003, the letter which says, in part, "visited John, his wife Sarah and boys Robert and William".
If we 信用d that （警察などへの）密告，告訴（状） enough to 原因（となる） us to put data in our database (that might be something for a 公式文書，認める about the source 文書), then I would 追加する the に引き続いて 入ること／参加（者）s to the database. First, there would be the 入ること／参加（者）s (which I hope are obvious) (in the People and Families （米）棚上げする／（英）提議するs) for any of the について言及するd people not already 現在の in the （米）棚上げする／（英）提議するs. Then, not so 明白に, we'd 追加する the に引き続いて...
ReID SDID PFID PF
1 sd003 0 f says: this doc tells us about "family 0" (John+Sarah)
2 sd003 0 p says: this doc tells us about "person 0" (John)
3 sd003 1 p says: this doc tells us about "person 1" (Sarah)
4 sd003 2 p says: this doc tells us about "person 2" (Robert)
5 sd003 3 p says: this doc tells us about "person 3" (William)Now... all spelt out for you like that, it seems like a lot of fuss! But it is a 事例／患者 of the old truism: "平易な to use = hard to explain". By the way: Most of the "neat, tidy" patterns in the numbers in the data are coincidental, just an artifact of how little data there is in the database so far.
With the structure of （米）棚上げする／（英）提議するs we have created, we can find out many things. And, by means not yet discussed, we can, when using our database, use 指名するs instead of all these wretched numbers and codes. So... questions we can ask....
What "Williams" do we know about?
Who in the database was born between 1800 and 1820?
We can ask "How do I know these things?" about any of the data in the （米）棚上げする／（英）提議する.
Who were Thomas Lunham's parents? siblings? wife/ wives? children?
Not bad!! If only finding the （警察などへの）密告，告訴（状） was as "平易な" as building the database to 蓄える／店 and to 組織する it!
Sorry for the abrupt 停止（させる）. The online copy of the database wasn't in step with all of the above and I went off to 直す／買収する，八百長をする that, then did another pass through the above, and now I'm の近くにing up shop for the day!
I dislike 'fancy' websites with more 関心 for a flashy 外見 than for good content. For a pretty picture, I can go to an art gallery. Of course, an attractive 場所／位置 WITH content deserves 賞賛する... as long as that pretty 直面する doesn't cost download time. In any 事例／患者....
I am trying to 現在の this 構成要素 in a 判型 which makes it 平易な for you to USE it. There are two 面s to that: The way it is 分裂（する） up, and the way it is 地位，任命するd. See the main 索引 to this 構成要素 for more （警察などへの）密告，告訴（状） about the way it is 分裂（する） up, and the way it is 地位，任命するd.
If you liked this Libre Office tutorial, see the main 索引 for （警察などへの）密告，告訴（状） other help from the same author.
Search this 場所／位置, SheepdogGuides.com, 含むing Flat-Earth-学院...
|
What's New at the 場所／位置 / / 前進するd search
This search 道具 (解放する／自由な to me and to you) is 供給するd by FreeFind.com... whom I've used since 2000. I'm happy with them... 明白に!
Unlike the clever Google search engine, FreeFind's 単に looks for the words you type, so....
* （一定の）期間 them 適切に.
* Don't bother with "How do I get rich?" That will 単に return pages with "how", "do", "I"....
公表，暴露: FreeFind tells me what people have searched for. It doesn't tell me your personal 詳細（に述べる）s. (If someone would "秘かに調査する" on you, wouldn't they also feel 解放する／自由な to 嘘（をつく） in a "privacy 声明"? Not to say I'm not lying... how can you tell?... but to say "What are privacy 声明s 価値（がある）?".
Please also 公式文書，認める that I also have other 場所／位置s, and that the FreeFind search will not 含む results from them. They each have their own 場所／位置-明確な／細部 search buttons.
My "wywtk.com" 場所／位置...WhatYouWantToKnow
My "skywoof.com" 場所／位置.
This is Sky. "skywoof.com" is 指名するd for her. (^_^)
And there are links from those pages to pages here at my SheepdogGuides.com 場所／位置, and at my Arduserver.com and Flat-Earth-学院.com 場所／位置s, which are also controlled by me.
https://www.arunet.co.uk/tkboyd/ My oldest-still-running 場所／位置*. Have a laugh at some 時代遅れの 構成要素! It may be 時代遅れの in styling, but not all of the content is obsolete. Much of what was there is also 利用できる at https://skywoof.com/aru/index2.htm (*My Compuserve 場所／位置 is, 式のs, history.)
To email this page's editor, Tom Boyd.... Editor's email 演説（する）／住所. Suggestions welcomed! Please 特記する／引用する the page's URL, "sheepdogguides.com/fdb/fdb7FamTree.htm".
Page has been 実験（する）d for 同意／服従 with INDUSTRY (not MS-only) 基準s, using the 解放する／自由な, 公然と accessible validator at validator.w3.org. It passes in some important ways, but still needs work to fully 会合，会う HTML 5 期待s. (Copy your page's URL to your clipboard before clicking on the icon, so you can easily paste it into the validator when it has 負担d.)-->
AND it has been 実験（する）d with...
Why is there a script or hidden graphic on this page? I have my web-traffic 監視するd for me by eXTReMe tracker. They 申し込む／申し出 a 解放する／自由な tracker. If you want to try one, check out their 場所／位置. Neither my webpages nor my programs 会社にする／組み込む spyware, but if the page has Google 道具s, they also 伴う／関わる scripts. Why do I について言及する the scripts? Be sure you know all you need to about spyware.
. . . . . P a g e . . . E n d s . . . . .