Split project members into current and former #29
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "msz/www.trr379.de:former"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
When linking to people, we need to deal with both attributions (not timed) and associations (time-constrained). Arguably, taxonomies are good only for the former, as they represent a simple, unqualified relation.
A contributor who left the project does not stop being a contributor in a broader sense, they may get listed as a "former contributor" in a project page but they should remain as they were in a publication page.
Changes made here try to keep Contributor as a taxonomy, while tuning the Project (term) and Contributors (taxonomy) layouts to differentiate between past and present contributors. This is done based on details declared in the front matter.
For project, a new custom template is created, borrowing from the existing contributor template. The loop showing links to other pages is repeated. First, we loop across current and past contributors declared explicitly in the page params (we first collect pages and then do a range sorting by "sortkey" param). Then, we do the standard term page loop over .Pages, only modified by adding a filter: where section is not contributors.
For all contributors, a new custom template is created, using the Congo's taxonomy template and repeating iteration over the terms twice, with filtering.
This means we rely on more information being included as page params:
params.activefor contributor, representing their overall status with respect to TRRparams.current_contributors¶ms.past_contributorsfor projectIt's probably better to rely on an external process to implement the classification logic and pass the result it in simple terms, rather than implement it in Hugo.
It also makes sense for an external process to set the contributors list in the project file (where it is being displayed) and the flag on a person record, because that process will likely have access to all the necessary associations when generating these pages. For the overall TRR "active" role, a person could be treated as inactive with all their project associations marked as ended (an edge case would be no project association, a decision likely depends on whether we want the person page to be more of a taxonomy listing or more of a project association listing).
Regarding "all contributors": one issue with the approach is that the parameter is set on /page/ but the taxonomy lists /terms/. This means, in the absence of DE pages for contributors, we will have access to
the "active" parameter in EN but not DE. This will lead to different listings. However, this is probably acceptable - several things are currently missing from the DE version. In any case, here we make some
provisions for the DE implementation by using i18n strings in the template.
Changes to provide the added params: q02/pool-publication-page#7
c688ab47c5to8ee24885bcWIP: Split project members into current and formerto Split project members into current and former8ee24885bcto39578c2e4539578c2e45tofc73667af9