![]() ![]() Something else you can do is look how the information you enter in the sources is formatted in the reports.įinally, no matter which way you decide to go, the most important thing will be that you are consistent with how you use them. Recently someone recommended Evidence Explained by Elizabeth Shown Mills, and I'm sure there are potentially many ways to add useful information to those fields that I'm not yet familiar with. Record type would be something like Digital image, microfilm, database. Record number should be something that helps you find that record back, the URL is an easy one, but it could also be referencing a specific microfilm number, book section, page, record number, or I guess a combination of all of the above. Publication could define if it's an original record, if you got it from a database online, if it's a picture you took or something like that? A few ideas of how I would use those extra fields now: ![]() There is enough flexibility that you can use those extra fields to add useful information for the future. That being said, I've been thinking about this as well for my migration to Gramps and being tempted by wikitree, and I wish I had added more details when I created some of them. They have also added the ability to color code your ancestors with up to eight different colors each. Any information you enter gets added to their trees, and vice versa. I went through my sources and the only fields I've ever used where title, place of issue (for me the place mentioned in the record or the relevant neighbourhood of the census), date (which I took to mean the date the record was created) and repository. This is perfect if you have relatives who are working on the same tree as you. I used to do the latter (separate sources for individual records), because the descriptive title was helpful when I needed to backtrack or double-check something. If this is the case, do you leave the title as United States Census, 1930? Or do you add more information to more readily find it in the list of sources? If any of you use this app, I would LOVE it if you could post some examples of how you have your sources structured, especially with regards to census data and some of the extra fields one can add: reference number, reference type, place of issue, etc. The ability to provide sources is extensive, but I'm curious as to what the best way to organize them is.įor instance, what would be the best way to go about using a Census source? Create a single source for all of my entries with the 1930 United States Census, and note the Page Number in the source citation on the individual's fact? Or should I create a separate source for each page of the census data, attach an image of the census page as the Media, and create a Source Repository called 1930 US Census? The latter seems to be the best way to go, as that's really where you add source media (e.g. This usually isn't a practical problem.Years ago I compiled a great deal of genealogical information, and I'm trying to get back into it/properly organize old research, and so on. If you have a base image that declares an ENTRYPOINT and a CMD both, and you redeclare the ENTRYPOINT in a derived image, it resets the CMD as well (very last paragraph in this section). There is one exception, and it's around ENTRYPOINT. (This is also true in Docker Compose a common question is about why Dockerfile steps can't connect to other containers declared in the Compose YAML file.) ![]() In the example you show, the COPY directive happens during the docker build step, and the base image's command doesn't take effect until the later docker run step. Since CMD and ENTRYPOINT just set metadata, the second image inherits this metadata.īuilding and running an image are two separate steps. When you have one Dockerfile built FROM another image it acts almost entirely like you ran all of the commands in the first Dockerfile, then all of the commands in the second Dockerfile. # Just remembers this in the image metadata doesn't actually run it Years ago I compiled a great deal of genealogical information, and I'm trying to get back into it/properly organize old research, and so on. Within a single Dockerfile this will work just fine: FROM ubuntu:18.04 Several of the Dockerfile directives (notably ENTRYPOINT and CMD, but also EXPOSE, LABEL, and MAINTAINER) just set metadata in the image they don't really do anything themselves. ![]()
0 Comments
Leave a Reply. |