Brian
I must disagree in a Graphical environment Tags are far more use than
Attributes and certainly the vast majority of mine are for the long term
Although I do use Temporary Tags as well and Attributes where appropriate.
phil
1 Like
@emyoulation
At first, I intended to write a response disagreeing with your position. I then decided to look up the wiki and read some forum posts about how people use tags and attributes. To sum up what I found: “There are as many ways to use Gramps as there are Gramps users” (I think this is a quote from somewhere, but I cannot find it right now).
My impression was (and most likely will be for my personal Gramps usage) that attributes are used for unique values (e.g. description, age at a specific event/source, identification information, etc.), while tags are used for grouping things (i.e. repeated value (tag name) for multiple objects). This is most likely driven by the user interface, for example not having suggestions for values used elsewhere for an attribute. However, some predefined attributes, such as caste, national origin and occupation contradict this interpretation.
That being said (and continuing to express my own opinon), I think that your “hashtag” idea with a comma-separated list of values moves in the wrong direction. Perhaps there needs to be another form to store information (maybe “Groups”/“Categories”), besides tags and attributes (either splitting the concept of tags between temporary and persistent, or splitting the idea of attributes between unique and categorizing data). I’m not saying that this idea would necessarily be beneficial for usability. It’s just an idea.
1 Like
For me, tags are for my use only as I work with the database. I would never add tags to reports or displays that I would provide to cousins as I share their branches of the tree. I want tags to be hidden as tools never to be seen by others.
1 Like
I use both Gramps Desktop and Gramps Web. One of the reasons for using Gramps Web is the “Blog” function - a feature to display stories. This is done by adding a ‘blog’ tag to a source.
I consider tags as simple single value data, while attributes are more complex data, e.g. 'height: 180 cm" or “profession: blacksmith”. So I would say that for controlling whether to show an image og not using a tag is a good choice.
1 Like
Based on what I found in other forum threads and the discussion here, I have decided to add another selector based on attributes attached to the media reference, available in version 0.1.160.
@emyoulation @DaveSch
Thank you for your feedback, as it is valuable in helping me develop an addon that works with different ways of using Gramps and different workflows.
When using the new options, you have to provide the attribute type and value. See the bottom right corner of the screenshot below for an example:
@comeng @csam
For those who prefer to use tags to mark images as signatures or coats of arms, the selector using media tags mentioned above is still available. Ideally, I would prefer to be able to attach tags to media references in addition to media objects, but that would be a different discussion.
2 Likes
Thank you for that decision.
Does the signature image have to be in the person’s media or is any event suitable for it (since the attribute is in the MediaRef it is attached to the person)? (I sometimes put the signatures in the person’s media and systematically in an Education Level event)
Edit: I’m wrong. The media is attached to the event attached to the Person. That MediaRef attribute is related to the event. I’ll put all signatures in Person’s media
1 Like
argh ! Version not available for 5.2 
@PLegoux
I have good news for you and everyone else using Gramps 5.2!
After some testing and finding no bugs, I just released the latest version (v0.1.162) of FTV for Gramps 5.2. It includes all the changes between v0.1.118 (the last version of FTV for 5.2) and v0.1.162.
You can find the (not so different) installation instructions here (you just have to use the right URL pointing to the gramps52 directory). Depending on how you previously installed FTV, you may be able to update it without doing anything special.
Please keep in mind that changes made to the 6.0 branch of FTV will rarely be applied to the 5.2 branch. Testing with Gramps 5.2 (by me and likely from the comunity as well) won’t be as thorough as testing with Gramps 6.0. Since the differences between Gramps 5.2 and 6.0 are not fundamental, I assume the chance of bugs in FTV for Gramps 5.2 that don’t appear in FTV for 6.0 is low.
If you have not kept up with the changes to FTV, starting here, the improvements that are new to FTV for Gramps 5.2 were discussed.
Please let me know your feedback and comments on the features added since then.
2 Likes
It works very well. Thank you very much.
1 Like
Persuading FTV (beta) to display children in a particular order
Gramps v6.0.1 with FTV v0.1.162 on Windows 10 and 11
I realise this is non-standard so I doubt there is a workaround…
I have created two dummy children in a family. Once called ‘seven children’, the other called ‘two children’. I’ve done that because that’s more or less all I know about these people. In between these two dummy children there is a real child. The Gramps IDs of the three are not sequential but that of ‘seven children’ is less than that of the real child, which in turn is less than that of ‘two children’ The birth dates of ‘seven’ and ‘two’ are spans, from 1796 to 1810 and from 1816 to 1819 respectively. The birth date of the real child is a regular date in 1814.
If I view this family in FTV then the two dummy children are both shown to the left of the real child but in the (Topola) Interactive Family Tree they appear either side of the real child. They also appear either side of the real child in the Life Line Descendant chart and are listed before and after the real child in the Pedigree chart.
I presume they appear in the ‘correct’ order in views that sort children on Gramps ID but it looks like FTV relies on birth dates but doesn’t pull out the start date of spans/ranges so it lists them out of order.
This in not a high priority for me but @ztlxltl is addressing this somewhere on your ‘to do’ list?
Thanks
Persuading FTV (beta) to display children in a particular order
OK, OK, the software did it on purpose, to make me look silly…
I’ve just returned to this family in FTV and now it is displaying the dummy children as I’d hoped, either side of the real child.
In other words, my problem has gone away so I don’t think there’s anything for @ztlxltl to look at here after all.
Sorry, for any confusion I may have caused.
1 Like
@stuck
The FTV should display the children and siblings of the active person in the order they are stored in the database, as well as all of their descendants, siblings, and aunts and uncles. Siblings of ancestors and their siblings are not ordered because they always appear on one side of the ancestor depending on whether the ancestor is the father or mother, connecting them to the active person.
Most likely, the active person is a descendant of the “real child,” meaning the “real child” is an ancestor of the active person. Since the siblings appear on the left, the “real child” must be the father, grandfather, great-grandfather, etc., of the active person.
If you notice an oddity like this again, it’s much easier to analyze the situation with a screenshot. You can use presentation mode to hide living people’s data or cover up information of other people by editing your screenshot.
I really need to document the logic of the tree so that people can pinpoint a rule that they believe is not being followed in a particular case.
Ah! That explains what happened. It was by design and not the code being vindictive and making me look silly by posting a non-existent problem.
I’m OK now. I understand 