prereview / prereview-standup Goto Github PK

Build out PDF.js display system (without committing to any particular design)

Needs migrating from previous implementation

Implemented in https://github.com/PREreview/prereview-standup/blob/master/client/components/review/compose.js

do they have an API for it?

• interface
• build out integration module
• connect up to plaudit

Migrate from pubsweet implementation

Similar to what eLife have done here:

From the eLife design links page.

This is a useful resource to create once lots of design things have been figured out, and a useful thing to keep in mind to maximise reusability.

Migrate logic from #25, #22

https://github.com/PREreview/documentation

We should recognise organisations and people that funded/enabled the project.

How about:

Simple strategic recognition in the footer:

• Community (collectively)
• Sloan as funders
• Wellcome Trust as funders
• CSS as fiscal sponsors

Then in the about page explicitly recognise the funders, any advisors or other people who it would be sensible to acknowledge, and specifically thank community members or groups who contributed to the development of the organisation and platforms.

All PREreviews from the v1 platform, https://www.prereview.org/, should be imported into the new platform. On v1 the prereviews are mixed in with articles and other types of content, so use the prereview tag filter to get actual prereviews.

Steps:

• research Authorea API
  • there doesn't appear to be a content API so I have started a scraper instead
• create an archive that can be directly imported into the database
• add archive import to the database creation script

We have consent from some PREreviewers to bring content to new site and assign DOI.

• @dasaderi to send email to those users and ask them to sign up in new platform.

• Daniela wrote to Authorea (Alberto Pepe) twice but got no reply for importing data and redirecting DNS. We will probably need to do this manually.

• implement testing and deployment framework

Implemented in user, team and admin models in PubSweet

Currently not working. The reason I want this to work is because, as I understand it, it will be necessary to activate the "solicit feedback" button on a user's profile.

Data transformations from the formats provided by source APIs to our internal preprint metadata model

Currently not loading. When I clicked on name of PREreviewer it brought me to a white page and it kept loading forever.

What we should see is a profile of that PREreview with info according to their choice of private/public profile.

https://certbot.eff.org/lets-encrypt/ubuntubionic-other

Ideally in general, and especially for projects with lots of contributors or where multiple teams might be responsible over time, sensitive information such as API keys, database configurations, etc, should be well documented and easy to control the permissions of.

This is a problem that is currently not well solved in general, and we are using a reasonable first approach given the scope of the project. We could make transitions between teams much easier by using a literate system, like (@mozilla/node-convict)[https://github.com/mozilla/node-convict]. Not urgent but will save costly developer time later.

We need a way for PREreviewers to add other authors to the PREreview.

We discussed the possibility of having a "Add a PREreviewer" button at the top of the editing box which creates a unique link that can be shared with another PREreviewer or a person who is not a user yet.

Another solution, perhaps more intuitive, is that the button opens a search box that goes through a database of PREreviewers but in that case the main PREreviewer needs to know the PREreview account name. Also this needs a way for the added author to confirm their willingness to be mentioned.

Text of the user profile interface

See #27

Linked to #14 and implemented in the same module

• project status
• version
• license
• travis

ideally a separate repo and we import it and compile it in at build time

• documentation lives in its own repo:
• https://github.com/PREreview/documentation
• backend integration in progress:
• initial MD-autocompiling setup:
• https://github.com/PREreview/prereview-standup/tree/master/server/docs
• https://github.com/PREreview/prereview-standup/tree/master/_server/docs

New continuously integrated version WIP

From home view and preprint view

The website currently isn’t responsive and doesn’t display properly on mobile or screens of a narrow width.

Done - diagrams to be uploaded

Extra controls for admins to display on:

• reviews (hide / delete / edit)
• comments (hide / delete / edit)
• user profiles (send template email, reveal identity)

Generalised components:

• https://github.com/PREreview/prereview-standup/tree/master/client/components/search

Home/main search page components:

• https://github.com/PREreview/prereview-standup/tree/master/client/components/home

Profile page search components:

• https://github.com/PREreview/prereview-standup/tree/master/client/components/profile

I no longer have access

• migrate issue labels
• migrate relevant issues from other repos and from airtable
• triage issues and assign milestones

lunr / solr integration with preprint and review metadata

Design process, tooling for remote collaboration, documentation of process, facilitation,
planning and system design:

• design managed via airtable and design repo
• remotes via Zoom, appear.in, and collaborative notes in hackmd
• develop docs

Interface for admins to send emails based on templates to resolve admin tasks

• Change last image on the right in the What We Do to new one

• Correct typo in What We Do "Train": last word should be "reviews"

• When launch, change the beta message to be "A platform for crowdsourcing reviews of preprints".
  Several users have reported the lack of clear understanding of what the platform is about. One suggestion was to adapt search to being the home page with clear message about what's the site is about and use illustration for resources and about page.

• Give feedback button in top bar should be red

• set up Travis integration
• configure runners
• debug test running

• user data store
• login / register components and callback views

Basic profile pre-populated from ORCID and with descriptive fields editable by the user

currently implemented within review display

Build a separate module, CLI and collection of modular adaptors

In development, we will use a dockerised postgres server, but because this is a small team project the cost/benefit payoff of using a managed db service is huge.

note: Details left out of the issue for security reasons.

offloads part of #19

Using ORCid