16.03.2017 (WM3) - AyranIsTheNewRaki/Herodot GitHub Wiki

Meeting #3

Opening:

The regular meeting of the [AyranIsTheNewRaki] was called to order at [9'oclock] on [16 March 2017] in [CMPE study]

Agenda:

  1. it is advisable for members to read about the research wiki before coming to the meeting

  2. starting with ERDs we will try to form an high level design of the system components

  3. finalize the project plan on ms project

    From https://github.com/AyranIsTheNewRaki/Herodot/issues/20

Attendees:

can, emre, idil, nur, onur (in alphabetical order)

Meeting Minutes

  • All the members attended the meeting having done their research on W3C web annotation data model, vocabulary and protocol from the latest release of February 23, 2017
  • all members had knowledge of standards, protocols of the semantic web in high level, in order to understand the web annotation model and its contributions to the semantic web as a whole
  • all members had the knowledge on anno4js, annotorjs and other commonly used frameworks
  • all members were up to date on linked data and json-ld
  • team members continued to focus on already accepted implementations and best practices and benchmarked according to the below:
    • hypothes.is for the annotation layer
    • europeana for the Cultural heritage item web site
  • mockups in line with EDM and hypothesis API were reviewed again by the team members to finalize the form fields and check its consistency with the EDM
  • europeana data model EDM and its available APIs were reviewed
  • hypothesis and its APIs were reviewed
  • test cases were created and Postman used to see the APIs capabilities after having understood all the above,
  • the team came up with a high level draft ERD for the CHO (cultural heritage object)
  • the team decided on utilizing the hypotesis API which meets all the required standards, protocols and requirements.

Open Issues

below assigned first person in the list of assignees is to be considered as SPOC for the issue (single point of contact), the issues will be handled in scrum meetings and status updates

Task Issue # Assignees Deadline Status
high level architecture formation #20 AyranIsTheNewRaki 16.03.2017 completed
Create project plan draft in ms project #18 Taygun Nur 20.03.2017 in progress
Create base project in spring #7 Emre Onur 20.03.2017 in progress
create base UI project #17 Onur Eren 20.03.2017 in progess
high level design and mockup finalized v3 #19 AyranIsTheNewRaki 16.03.2017 Complete

New Issues

Task Issue # Assignees Deadline Status
Create draft ERD sequence system component diagrams #21 Nur taygun 20.03.2017 in progress
draft a feasible hypothes.is API modification in line with system requirements #22 Can Nur 20.03.2017 in progress
mobile design and development v1 #23 Idil Emre Onur 20.03.2017 in progress

Agenda for Next Meeting

  1. status update of the open issues and progress
  2. updating the project plan with the latest issue progress
  3. decide on the new issues depending on the progress and customer feedback

Adjournment:

Meeting was adjourned at [11pm]. The next general meeting will be at [9pm] on [ tbd date] in [tbd location].