This needs a fresh look on the development side. The work that was done before may be a good basis from which to start, but does not have to restrict the solution. The comments here provide guidance on various nuances.

Hello all! We would love to see this implemented. Since this bug hasn’t been commented on in a bit, wanted to put out there there are still institutions who would like certainty conveyed to the public.

Since this migration is getting complicated and the pull request has gone through a lot while the main branch has kept moving forward with other migrations, is going to take this on.

Thanks for the comment !

while you’re already working on the piece of that relates to adding Certainty to the trees where appropriate, the other part of Cory’s comment, relating to whether or not to leave off Certainty when there is a date expression, is useful nuance. We can talk more about this when we meet. It should be all or nothing (i.e. do not include Certainty to date expressions in the areas addressed by this ticket ), not a config option.

This appears to be working as described, but the application is not entirely consistent and may not be desirable in all cases. The qualifier is currently appearing in parentheses in the staff interface as part of the title label for archival objects, and in the public interface as part of the title label for archival objects. In the public interface it also appears following the date element display for archival objects. It does not appear in the Collection Organization navigation menu in the PUI, nor in the tree navigation in the staff interface.

However, while the addition of the qualifier may be helpful in some cases, it may be undesirable for institutions that record qualifying information as part of their date expression entries. For example, if the phrase “approximately 1950” is recorded in the date expression field the display will now show the duplicative version “approximately 1950 (Approximate)”.

It may be better to limit this display qualifier to cases where the date expression field is not used. Alternatively, this could be a configurable option that could be enabled at a instance or repository level depending on local practice.