Presentation overview of user feedback on current “labs” (Stella)
Curation/Curator side:
Status of queues (Bernard)
Status of curation workflows (DESY)
Author disambiguation (Micha)
Current workflows
Gaps
Tools used (scripts)
We'll discuss feedback received on the new version: what we've learned, what is to be implemented, improved, etc.
Production
- We'll single out short- and mid-term issues regarding the reliability of the production site and its services.
- SLAC OSTI-INSPIRE workflow integration
We'll discuss INSPIRE's mission, vision and strategy for future projects and development; define next steps, and plans, 2-5 years ahead. How does what we are today translates into what we want to become. We're looking to a fruitful discussion about various topics, ranging from crowdsourcing to record submissions (by users; online first; auto-accept/reject; automated CORE guessing...).
First, we'll discuss the importance of the Advisory Board - its purpose, and role, but also whether we still need it. Could we change its role?
To this end, we'll share ideas about new considerations, such as INSPIRE's new Ambassador Program. We'll discuss the suggested one, and see what suits INSPIRE best.
Governance calls - do we continue as it is?
Data on INSPIRE, HEPData
We'll see what's ahead, compare the current and future state of our project, specify priorities, expectations, and next strategic steps to take in order to achieve our goals.
Stella will start a discussion on our vision, so we could agree on and approve future milestones. We'd see how we could work 3-5 years from now - improve curation, among others.
We'll do a facilitated exercise for easier brainstorming.
We'll discuss more technical/practical side of our operations, such as the following:
1. What tools are needed to simplify/semi-automate user submitted corrections (of references/citations in particular)? (“smart forms”)
Shall users be able to add/correct info of their own papers (which fields)?
Collaboration tools: currently email/zulip/hangouts/asana/drive/github/gitlab/JIRA/RT/… need to unify/simplify?
Operational: GDPR, Institutions and smart formsTBD
TBD
1) GDPR
2) Smart formsWhat tools are needed to simplify/semi-automate user submitted corrections (of references/citations in particular)? (“smart forms”)
Shall users be able to add/correct info of their own papers (which fields)?
We'll discuss back-office matters, such as the status of manual merger (for journal harvesting), curator labs login (only ORCID or to include local account?), and display formats (WG to play with mock-ups? Can we afford a curator display in addition to brief and detailed? Can brief be (re-)used for references, holdingpen?). We'll look into examples where code structure is not optimal - and talk about how to avoid this.
