[Proceedings Metadata] Tool to create and deposit proceedings issue metadata

Feature Request

Description

We lack the infrastructure to create and deposit the metadata related to an issue within SciPost Physics Proceedings.

Proposals

Add Editorial Administration tools to manage metadata of SchiPost Phys. Proc. issues. Among these tools, we need:

• Create/update XML metadata
• Editor to format XML metadata
• Deposit XML metadata to Crossref
• Mark metadata deposit as succesful/unsuccesful

The metadata prepared should include at least the required elements defined by Crossref for conference proceedings and if possible the recommended and optional elements.

1. Proposal 1 These tools can be added in a section of the issue page, e.g. https://scipost.org/SciPostPhysProc.X, accessible only to EdAdmin.

2. Proposal 2
   Create a specific page to Manage Proceedings issue metadata. This page should be linked from https://scipost.org/journals/admin/manage_metadata/, and should include the same navigation menu interlinking it to other metadata management pages.

added impactlow prioritymedium typefeature ⭐️ labels

added priorityhigh label and removed prioritymedium label

changed iteration to Two-week Sprint Sep 8, 2024 - Sep 21, 2024

added time estimate of 3h

assigned to @gkatsikas

added workflowin-progress label

changed the description

added 2h 10m of time spent

marked the checklist item Create/update XML metadata as completed

marked the checklist item Editor to format XML metadata as completed

marked the checklist item Mark metadata deposit as succesful/unsuccesful as completed

marked the checklist item Deposit XML metadata to Crossref as completed

added 1h 20m of time spent

added workflowready label and removed workflowin-progress label

mentioned in commit e3682390

closed with commit 0afd2ef8

added 20m of time spent

This has been implemented according to the conference proceedings metadata guide, but our format may be more suited to a simply creating the publication metadata with an appropriate issue tag instead as in the articles guide.

mentioned in commit 0afd2ef8

mentioned in commit c16c5863