Family Historian User Group

Requirement

To be able to access the File Description field in the GEDCOM Header (accessed normally via View > Special Records > Header Record) when creating or opening projects.

Benefit

Making the "File Description" more accessible helps with management of projects. If the contents of this field (or the first x characters of it) show as either a tooltip when mousing over project names in the Project Window, or in a subsidiary display field (say below the list of projects but above the three buttons), the project description can be read. This means that the project name does not need to be over-loaded with data to enable identification of projects (which could run into path name length issues). To assist adoption of this feature the create project dialogue needs to prompt for a "File Description".

Associated Discussions
Project opening warning/notice (21226)

As stated in the above mentioned FHUG thread, I would support this idea.
If the use of the 'File Description' cuts across its use by others, perhaps another field could be used?

Is this related to Wishlist: Provide a “Program Ready” event in API (16796)?

I quickly read the thread you linked to and from what I could understand, this 'Wish' is not the same.
It has been motivated by the discussion in this thread.

Project opening warning/notice (21226)

peterbel wrote: ↑14 Dec 2022 22:49 I quickly read the thread you linked to and from what I could understand, this 'Wish' is not the same.
It has been motivated by the discussion in this thread.
Project opening warning/notice (21226)

That was my intention (although the link is dead and has been amended)

Am I missing something here, surely a solution was suggested in the above post, whereby " (%CUR_FILE_HEADER.NOTE2%)" could be inserted into the property box title, so file descriptor is readily to view at all times, simply by looking at Property box header.

I have used this method quite successfully to remind me of the contents of the current open project e.g Direct Ancestors only or All Ancestors etc

I want the user:

• to be able to read "a descriptor" at the stage where a project is opened - from the project window,
• to be prompted (optionally) to enter a description when going through the project creation process

It's also the case that the Property Box Header is too small to display a substantial descriptor.

There seem to be several lines of thought, not surprisingly, so to be clear.
My preference would be that brief information about the Project would be available before a project was open, like a tool tip is when the cursor hovers over an action button. That way when I have several Projects listed I am not reliant on just the Project name to help my selection. The suggestion of where that information is stored was that it could possibly be in 'File Description', but I don't know if that has adverse implications.

Amendments 15-12-2022 mainly clarifications and moving explicit reference to the File Description Field into the Notes
Additions in Blue/Italics
Deletions in Red/Strikethrough

Allow use of a 'File Description' when in the Project Window creating and opening projects

Requirement

To be able to access the see a File Description field in the GEDCOM Header (accessed normally via View > Special Records > Header Record) when creating or opening projects.

Benefit

Making the a "File Description" more accessible helps with management of projects. If a description can the contents of this field (or the first x characters of it) show as either a tooltip when mousing over project names in the Project Window, or in a subsidiary display field (say below the list of projects but above the three buttons), the a project description can be read. This means that the project name does not need to be over-loaded with data to enable identification of projects (which could run into path name length issues). To assist adoption of this feature the create project dialogue needs to prompt for a "File Description".

Notes

1. This might be achieved by use of the File Description field (accessed normally via View > Special Records > Header Record)
2. To assist adoption of this feature the create project dialogue needs to prompt for an optional "File Description"

Associated Discussions
Project opening warning/notice (21226)

Sorry, a bit late to the party I'm afraid!. Not seeing anything in David's final "requirements" post indicating if this File Description value will be mandatory or optional?.

jbtapscott wrote: ↑15 Dec 2022 17:39 Not seeing anything in David's final "requirements" post indicating if this File Description value will be mandatory or optional?.

I'm anticipating "optional", but would suggest that documentation describing the use of the File Description field (or whatever CP decide to use) should stress how text, particularly at the beginning of the Field can be used to offer "description" in the Project Window and therefore its use is recommended in preference to complex naming of the project?

I see no value in making it mandatory, no "processing" depends on it.

Thanks David - I would agree that Optional is best but thought it best to flag that the description said neither!

I've added the word optional in the notes.

When I am trying to formulate a wish list item, I try to put the "what I want" at fairly high level (I don't want to do CP's job for them) in the "Requirements" section.

The "Benefits" section is the "why I want"

The "Notes" section is very much supplementary giving more detail and highlighting any particular issues.

Wish List item 592 has been created.

In the Wish List, the Associated Discussions link to
Project opening warning/notice (21226)
is broken because it uses https://fhug.org.uk/wishlist/viewtopic.php?t=21226 instead of https://fhug.org.uk/forum/viewtopic.php?t=21226

Thanks Mike. Fixed.