I like the tag feature, but I’m frustrated that there aren’t any tags to begin with and that they have to be created manually. I can think of a few preset tags that could be added for people, such as research status, war veterans and people who held royal or noble titles. I don’t know how you would implement this, but it would save me time.
While we’re on the subject, it would be great to apply tags to all the ancestors and descendants of a person. For example, I could create a tag for everyone in my family tree who descends from a specific person, and then apply it to all of that person’s descendants. This would save me from applying the tag to each person individually, which could take a long time, especially for those with hundreds of descendants.
That could do the Ancestors or Descendants tagging.
You can also Filter one of the “list” views and/or select all or some of the records in that View to choose to apply or remove a tag en masse.
For the example below, the Example.gramps sample tree has been imported and a non-sensical Filter was applied (which finds persons with both an “i” and an “a” in their name, born in a place that contains the word “town” and who have a “Death” event). Then 3 rows were selected from the filtered list. And finally, the “ToDo” was applied to those persons.
I prefer to utilize Tags differently than many other users. I’ll use Attributes for permanent data and Tags for temporary filtering or temporary color coding. Otherwise, the Tag Add/Remove double-entry menu becomes quickly overwhelming.
In this menu, there’s more than a screen-full of “Add” menu items with just “A” through “S”. The rest of “S” through “Z” and the “Remove” menu items for “A” through “Z” will take more than another screen-full.
The problem with creating a set of packaged tags is that there are as many ways to utilize tags as there are Gramps users.
I too tag branches of my tree. I have a set of filters that finds the ancestors of the active person then brings those lines forward. I do this for my four grandparents. Once the filtered list is returned I can select all and apply the tag to everyone at once.
I think that we could just start off with tags based on research status and go from there.
Just in my case, I have many different types of tags; these include people who descend from certain monarchs, specific officeholders, people who owned slaves, etc.
For officials and slaveholders, I find using an “Event” to be preferable. That allows structured recording of places and time-frames and have those be separately searchable characteristics.
There are built-in Events for assuming Nobility titles, Elected office, Military rank, and so forth. I added “Slaveholder” as a custom type. And the event can be ‘shared’ to the enslaved persons with a custom “Enslaved” role. So the crime, offender and victim can be thoroughly linked.
I am in the no Preset Tags camp, the bigger problem really is that Tags
are not handled the same across all views GraphView being one of the
notables
phil
I only use tags for the research status of the profile. This keeps the list short. Long lists are cumbersome. I would likely not use preset tags such as Nobility as I don’t have any in our family. Tags are a workflow tool and there are very many ways to use them.
