# Background In an effort to simplify the user experience and unify our reference matching tools. Crossref is building the "Reference match & deposit" web tool. Objectives: - Direct users to the right kind of search - Provide a UI to search Crossref's metadata - NOT another Google Scholar or WoS/Scopus # How urgent ??? [comment]: # (No need to update the Definition of ready when filing issues, but feel free to have a go if you're familiar with the territory.) # Definition of ready - [ ] Product owner: - [x] Tech lead: @yaffol - [ ] Service:: label applied - [ ] Definition of done updated - [ ] Acceptance testing plan: screenshare / demo on product owner's machine (via docker-compose) - [x] Weight applied [comment]: # (Feel free to leave this as is, or suggest changes. We'll update these during Backlog Refinement, prior to bringing this into a sprint.) # Definition of done - [ ] Unit tests identified, implemented, and passing - [ ] Code reviewed - [ ] Available for acceptance testing via a staging URL, or otherwise - [ ] Consider any impacts to current or future architecture/infrastructure, and update specifications and documentation as needed - [ ] Knowledge base reviewed and updated - [ ] Public documentation reviewed and updated - [ ] Acceptance criteria met - [ ] xState State Machine defined and visualised - [ ] Cypress e2e tests defined and passing - [ ] Citation style can be chosen via a drop-down menu - [ ] References are re-rendered (likely via and API call) on citation style change - [ ] Acceptance testing passed - [ ] Deployed to production # Notes [comment]: # (By default all issues need to be labeled Planning::New, only remove if you know what you're doing) # Design specification https://xd.adobe.com/view/cbaf5b3f-9556-43d7-9c7c-58e0eacc8c4f-9efc/screen/613e57e8-4c79-43c4-98f1-445b8293173d/