D3.1.3 Build project discovery tool

[tms-epcc]

(D3.1.3, Mar 2024) Build a project discovery tool to enable researchers to identify projects with similar datasets to their own during the building phase; this is essential to avoid the accidental deployment of multiple projects addressing similar problems, which would lead to the fragmentation of the volunteer community and effort.

[tms-epcc]

03/AUG/23

• Chris to add this deliverable to the EPO plan at https://docs.google.com/document/d/12KeT_mN3CG1Yu7Mra8vXPCzZAurm4ushZdLudG66chw/edit?usp=sharing

[tms-epcc]

25/AUG/23

• deliverable added to the EPO plan in the google doc under Validation at the WP-PM meeting
• @chrislintott reported that much of this deliverable has already been built on the Project.
• Eric Rosas, the EPO developer, will therefore be looking at this

[tms-epcc]

19/JAN/24

• @chrislintott reported that the Oxford Zooniverse team are supporting the Rubin EPO team with this task.
• Currently expecting this to be ok.

[tms-epcc]

27/MAR/24 @chrislintott reported

• EPO team want to stop the creation of duplicate projects.
• Intention had been to identify possible duplicates at the project creation stage when data is uploaded
• But.. the data identifiers are changing from one data release to the next and so an automated means of doing this does not seem possible.
• Rubin EPO team are instead implementing a manual system where a record of projects is kept and updated.
• This requires the creation of a policy document which Chris will write.
• This policy document with for this deliverable D3.1.3

[tms-epcc]

24/APR/24

• Draft submitted by @chrislintott for review
• @tms-epcc to insert into the LSST:UK deliverable prior to circulation to reviewers
• @chrislintott has proposed two reviewers @tms-epcc to confirm reviewers with PL and PS.