stewartmcgown / article-management

API for managing articles

Once upon a time I was an environmental entrepreneur

---

article-management's Issues

Add all GraphQL decorators and resolvers

Author information is fragmented

All authors information should be added either to article database rather than a Google Doc. Will save fragmentation.

Decide method for Plagiarism checker

What does it need to do?

• Identify existing text snippets on websites
• identify existing text snippets from books

Sources for information?

• Google
• Bing
• Paid copyright services?

Get articles by editor email

Will allow front end to get articles that are assigned to this user. Easier with graphql.

Expose an `articles/create` endpoint

Only allow documents that can be converted by Google Docs

Marking grid link off by one

Dropdown for finding editors

Articles should go through a 'flow', with ability to manually change status

There should be ordering to article status. For example, 'Submitted' is generally promoted to 'Technical Review'. This should be configurable and the API should recommend that the next status option be that'.

{
    "promotesTo": {
        "id": "uuid-string",
        "name": "Technical Review",
        "color": "blue"
    }
}

Add Policy and Ethics team

Create a WebSocket wrapper around exisiting CRUD operations

Allow authors to view just their own articles

WordPress status built straight into dashboard

View live status of an article on the WordPress site with a async icon, or drop-down. Ability to publish, update tags etc could be done through the API.

Removes need for people to have access to the WordPress site, and can allow junior editors more control over the site than would previously be possible.

Add copyright notices to articles

Notices like:

[{
   "image": "url",
   "sources": ["url1"],
   "royaltyFree": false
}]

Request images from an article

Google Docs has the ability to export as a word document. These documents are basically ZIP files that contain text and image files.

Using ADM-ZIP, we can extract these images from the document, re-zip them and send them back to the user.

View all comments on a Google Doc

See which editors have an article assigned

Reverse image search to check where image came from

Search doesn't work with Enums

Add levels of access to actions

Senior/Junior positions should be different. A junior editor should not have the ability to delete articles, change their status etc.

Replace most enums with a table

Things like subject, status etc should not be hardcoded

Implement retry limits for OTP

Partial responses for queries

Allow only partial results to be returned, for example only the last 2 days of articles, or only articles in the Technical Review stage.

Choose authentication method for Websockets

Async HTML to stop massive load time

Add way to 'dissociate' editors from article

Perhaps using a DELETE request to the /assign endpoint

Events should trigger a push to clients over websocket with changed data

Provide information on editor subjects

Notifications during status updates

Script requires login when using paths

Script will not execute and will prompt for login details when trying to execute without a user logged in.

For example, https://script.google.com/macros/s/AKfycbxGlDi_tCifqCC-tBfJ5mK1VDNi2t6Qa8ClNexIeOr1Ll59nodb/exec/authentication/authenticate, will not work without any Google user signed in.

Switch from custom Google Sheets DB to PostgreSQL

Add ability to 'flag' articles

These articles should be pinged to Senior editors that moderate the subject attached to the article.

Implement pure passwordless

Emails are passwords.

Some sort of time-based authentication, where PINs are issued and validated into authTokens.

PIN

Request

POST /auth/pin
{
  "email": "[email protected]"
}

Response

{
  "message": "success"
}

Token

Request

POST /auth/token
{
  "email": "[email protected]",
  "pin": "FG76H6"
}

Response

{
  "token": "abdfgbsd9fgbsdfgsdkjfgbsd89fgbdsfiohgbdfgvdsfbnvd8f97vh98sdfn"
}

Implement a better AuthenticationResource

Current AuthenticationResource sucks. Should contain user data of appropriate anonymity.

AuthenticationResource {
level: Enums.AuthenticationLevel,
message: String,
editor: Editor | PartialEditor
}

A partial editor can contain as little as an email.

Start copyright job when articles are submitted

Allow multiple photos to be uploaded with Article

Authors should be able to attach a photo per author.

To receive these will probably require expanding the arguments of the create controller method to accept extra uploaded files dynamically. This can probably be done with an array of some sort.

Dispatch plagiarism checker on article create

Authors should be created and notified when articles are

Authors should be notified when:

• An Article is created under their email
• An account is created for them

Asynchronously fetch info on Google Docs

Document metadata, like last updated, number of comments etc

Prepare all models in TypeScript

Create and validate all entities in typescript. Use the class-validator and typeorm npm plugin to make this happen.

Add wordpress upload capability

You should be able to click 'Publish To Wordpress', get ability to edit Title etc, then confirm and the article should go on to the Wordpress site.

There is already a basic implementation in the master branch

Add status of '2nd Editor Required' and 'Ethical Question'

Keep track of who has executed what action on an article

Display user profile picture next to their article