Melissa Harrison

I second this request. Using the DataCite API I cannot identify Peer review items if they are not given the appropriate resource type

>this is possible, but is it really MVP? we would suggest to move such things into separate feature-request tickets to be addressed in later iterations. We've agreed to sign off...

@michael can you explain what you mean by auto suggestion? This is not mentioned here in our ticket. We've not asked for it here. We're being explicit about what we...

Agreed. We're happy to restrict this in our Schematron validation outside of Texture. As a vanilla tool, Texture should not be a restricted tool. Sorry, it's a communication issue, that's...

>Can you maybe remove those considerations from this ticket for brevity I'd rather update the considerations to indicate eLife will deal with that requirement in our own validation tools. That...

Have updated the consideration to be clearer as to what we mean: >We are not putting a `` in for authors to indicate they are authors (eg `Author`; any person...

@michael Updated consideration: eLife only allows suffixes for authors and then only a select few (we don't allow PhD or MD for example, just Roman numerals, Jnr and Snr). Other...

@michael I have pulled this out of the ticket but it is kept here for now. They cannot be in the ticket without user stories attached to them. ## Figure...

Yes I agree. Shall we pull in the figure metadata ones here and close the ticket https://github.com/substance/texture/issues/1249 The tickets we're generating have good user stories that have been verified by...

@michael Thanks for this. @NickDuf and @oliver---- we've been thinking inhouse about how to tackle references. It feels like it is a massive topic that needs further group work before...