Accelerator 4th Meetup MVP Discussion

19.10.16 Present- Oliver, James, Cedric, Kylie, Laura

Cedric no longer has time for this project due to imminent CodeFirstGirls commitment, so declared that he wished to handover and sign off the work he’d done at this meeting. Cedric has documented his work on GitHub and will make sure this is left all in good order.

Update from last two weeks

Cedric: Back-end

Clearing up API endpoints e.g. As a user I want to get all of these facts reliable to database- get paragraph. Collate what I want Get facts. Relates to Hypothesis. User clicks on fact- goes to backend; saves in JSON format to database Later date query- what are top 100 facts?

James: Frontend

Tim eplicated Hypothesis front-end Hypothesis license is okay Hypothesis offer funding for other projects e.g. SciBot funding

TO DO:

Cedric:

Get fields in usable state by filling placeholders Currently only questionable facts Move to verifiable facts Fact can then switch from questionable to verifiable Currently simply bare-bones prototype

MVP for attaching back-end to front-end: (See what Hypothesis API outputs) -Able to extract and send somewhere -Tell it to annotate something

Q. Retrieval from database? -Separate problem!

List of end points of fields to save When two points connected and can see date

User testing- collect feedback over next two weeks

Functionality of front-end? need to: download plugin; highlight fact; identify question; know the email to respond to

Q. Stick to Hypothesis or use own code? If stick to Hypothesis- they keep data can’t use AI unless we can grab data but need to tell user third party is involved Using Hypothesis and tags would be problematic Therefore better to use our own code rather than borrow Hypothesis Can the code Tim has retrieved be altered?

UX TO DO:

Kylie/Oliver: User test prototype

Kylie: Value proposition testing

Oliver: Competitive analysis

N.b. In Cedric’s absence Laura agreed to take the technical lead for next two weeks