Question Concepts for organizing a genealogy in webtrees as an archive

For web sources I have the main page of the site in the Source object. The full url of the detail page then goes into the source citation of an event.
Then usually no further (shared,) notes are needed.

Jefferson49 wrote:

However, while thinking about the resulting data structures, adding shared notes to the source citations raises some doubts from the Gedcom data model point of view: The URL to a source should be directly assigned to the source itself and not to the source citations, which might multiply the information. It seems that assigning it to the citation is only necessary to see the link in the webtrees front end for facts/events.

I believe it is acceptable to do either or both. The PAGE tag is provided for this purpose, to specify a location within a source. It's just that it applies to INDI:SOUR and not INDI:SOUR:NOTE, so there are some limitations built in. I prefer the note simply because it prevents duplication when more than one individual is grouped on a page/object/whatever. I don't follow the gedcom suggestion to track individual line numbers.

bertkoor wrote:

For web sources I have the main page of the site in the Source object. The full url of the detail page then goes into the source citation of an event.
Then usually no further (shared,) notes are needed.

Sounds very logical to me. Where do you put your URLs within the source object? And where within the source citation?

miqrogroove wrote:

The PAGE tag is provided for this purpose, to specify a location within a source. It's just that it applies to INDI:SOUR and not INDI:SOUR:NOTE, so there are some limitations built in. I prefer the note simply because it prevents duplication when more than one individual is grouped on a page/object/whatever. I don't follow the gedcom suggestion to track individual line numbers.

o.k., I understand. If the URLs have the character of being citations (like in the post of bertkoor), they should be located within the citation. For reuse within other citations, the shared note is helpful.

Jefferson49 wrote:

Where do you put your URLs within the source object?

There's a field called "Publication", tag PUBL. But you can also add the tag URL.
Either should work.

Jefferson49 wrote:

And where within the source citation?

In the field "Citation Details", tag PAGE.

Just recently, I have published an update of the "Repository Hierarchy" custom module. The new version now supports most of the use cases, which I described in my initial post.

• Publication notice in webtrees forum
• Github repository for custom module and Readme file
• Download custom module

miqrogroove wrote:

Also, same concern applies to CALN where webtrees does not pull that value into the facts/events tab. This only happens with the PAGE value in citations, which in turn doesn't apply to notes. That leads me back to the need for either markdown or custom code.

The latest version of the Repository Hierarchy module contains a feature to show additional information within the source citations in facts/events. Specifically, repositories, call numbers, notes, and user reference numbers are additionally shown. Maybe, this feature might also be useful for some of your linking use cases with Collective Access.



A description is included in the corresponding chapter of the Readme file .

miqrogroove wrote:

As I add "objects" to the archive, they are assigned an autonumbered URL that is also independent of the object data. So I am continuing the use of Shared Notes in webtrees, and simply adding a markdown link to the archive object's URL, then using the shared note on individual source citations.

In the latest version of the Repository Hierarchy module, I managed to include a feature, which automatically provides links from webtrees source citations to AtoM records. In AtoM it is possible to tell the system to generate REST URLs from call numbers or titles. Since call numbers (or titles) can be kept the same between webtrees and AtoM, links can be generated with an algorithm.



If you have some ideas for a simular REST URL concept with Collective Access, I can offer to implement an additional feature for Collective Access linking into my custom module.

Jefferson49 wrote:

The latest version of the Repository Hierarchy module contains a feature to show additional information within the source citations in facts/events. Specifically, repositories, call numbers, notes, and user reference numbers are additionally shown. Maybe, this feature might also be useful for some of your linking use cases with Collective Access.

This should be useful in many situations, especially if URL values are supported.

I'm very happy with my markdown links so far.

I really don't know if Collective Access offers some kind of identifier-string-to-autonumber responder. Even if it did, using such identifiers would require maintaining those numbers in 2 different systems, where they are editable in both places. So I'm not sure where the call number vs. URL debate ends.

There are signs of new momentum toward a v2.0 release of CollectiveAccess.  This could be a game changer with added support for PHP 8, better flexibility for PDF displays, and more quality updates.

Documentation is still a weak point.  There doesn't seem to be an official feature list out yet.

miqrogroove wrote:

There are signs of new momentum toward a v2.0 release of CollectiveAccess.  This could be a game changer with added support for PHP 8, better flexibility for PDF displays, and more quality updates.

Documentation is still a weak point.  There doesn't seem to be an official feature list out yet.

Sounds interesting!

For Importing data from webtrees to CollectiveAccess, the EAD export of the RepositoryHierarchy custom module might be an option: See  Readme.  In the CollectiveAccess documentation about data import , an EAD import is mentioned. However, it is also described that an " Import Mapping " might be necessary

For myself, I do not further investigate external archive tools. My most important use cases about archive management are covered by the RepositoryHierarchy module directly in webtrees. Further use cases like media management/presentation, where external tools offer significant improvement, are not that important for me.