Zooniverse design changes due to template project

[tms-epcc]

Item 4.a in the EPO agreed outline plan -Zooniverse: Q3 '23 to Q2 '24 (Note mis-numbered as 3)

Make changes to Zooniverse design if required for template project

[tms-epcc]

19/JAN/24
@chrislintott reported in https://docs.google.com/document/d/13mgVp2T9EWWeuTVkvrf_WEW-xG721zaSsmiCrAdWHwo/edit?usp=sharing
the following as completed
2. Creation of Template Projects
2.1 Template created and populated :
- First Template: Project Link / Lab Link
2.2 Project copier bug fixes
- Project Copier Issues (issue 1 & issue 2): resolved (PR link)

[tms-epcc]

29/MAY/24
from FY24 Q2 QU

• Improvement documentation of project specific features (see summary document here: https://docs.google.com/document/d/15jR9EQYYfY_1ytWbaN9YBoRckJ9MDNM4_b7ipG3AoQg/edit?usp=sharing)

@chrislintott reported

• have documented what will be done for this but now waiting for spec from the Rubin EPO team.

[tms-epcc]

From draft FY24 Annual Evaluation

We assume that most projects instantiated by the transfer of data from the RSP will use one of a series of templates. At the most basic, this may just impose Rubin project logos and styling, but we anticipate that we will provide a series of templates for common patterns; e.g. a standard project for light-curve inspection that would include automatically a choice of subject viewer, task, and perhaps even standard questions. Work this year added to the Zooniverse API to support this need for multiple templates.