GSOC 2019: Patient Flag Module OWA

1st GSoC Weekly Call

Held On: 17/05/2019 : 11 AM CDT

Participants: @maimoonak, @judeniroshan , @rakshir

Minutes of Meeting:

  1. Meeting began with a quick bout of introductions from mentors.

  2. Task given by @maimoonak has been completed. ‘Demo App’ project is required to be uploaded to GitHub and shared. [GitHub Link]

  3. Problem faced with trying to create the project with Yeoman Generator faced. Getting a 404 Error at App Entry Point URL despite following steps here correctly.

  • Resolution: Discussed the issue. Will try to resolve by 2nd GSoC weekly call. If not resolved, mentors shall help resolve. To ask in OpenMRS Talk thread so that help from the community can be taken at large.
  1. Integration of openmrs-react-components has been deemed as important. Since documentation is a bit sparse, have been suggested to use as reference and integrate openmrs-react-components into the ‘Demo App’

  2. Advised to try style-referenceapplication as a styling guide for the OWA. Try it on the ‘Demo App’

  3. Date for next Weekly Call to be fixed.

  4. Meeting ended on a positive note, looking forward to a greatGSoC. :slight_smile:

Tasks for the Week:

  1. Upload ‘Demo App’ project files to GitHub [GitHub link] :white_check_mark:
  2. Try to resolve Yeoman Generator issue. :on:
  3. Examine openmrs-react-components and try to implement it in ‘Demo App’. :on:
  4. Examine Patient Flag Module endpoints - {23rd & 24th May}

LEGEND:

:white_check_mark: - Completed

:on: - Ongoing

{Date Range} - Planned

Next Weekly Call:

Hi all, unfortunately we couldn’t do a weekly call earlier this week. Hence, will Thursday or Saturday at 11 AM CDT be a good time? @maimoonak & @judeniroshan.

NOTE: The following is our public GSoC Calendar link: LINK

Have you checked https://www.npmjs.com/package/@openmrs/generator-openmrs-owa?fbclid=IwAR29XQJ-1jb0JyXD8KgDSbClYftyU5fZ5MWyGR0fZZip3U1gjRnZHs0-nNg

Yup. This is the Yeoman Generator npm package where I’m facing the issue. Everything is fine, it’s gernerating the scaffolding properly and the build is successful as well. But I still see the 404 error at the App Location. One thing, it wasn’t automatically putting the build files at the Local OWA directory after building. So I manually put the build files in the local OWA path. Still, no luck.

Weekly Meeting 2

@maimoonak @judeniroshan

As per plan, the second weekly meeting is being held this Saturday at 11 AM CDT. Meeting Link:

Cheers!

@maimoonak @judeniroshan

I’ve managed to resolve the Yeoman Generator & the 404 error issue. I basically had to change the manifest of the owa and add the “folderName” and “launch_path” attributes as below and it worked! :slight_smile:

“folderName”:“demoapp”,

“launch_path”:“index.html”,

1 Like

GSoC Sprint Planning

Type: Meeting

Agenda: Planning upcoming development sprints.

Participants: @maimoonak , @judeniroshan & @rakshir

Location: Skype

Date & Time: 26/05/2019 - 11 AM CDT

2nd GSoC Weekly Call

Held On: 25/05/2019 & 26/05/2019 at 11 AM CDT

Participants: @maimoonak , @rakshir

Minutes of Meeting:

  1. Yeoman Generator issue solved - scaffolding can now be created for the OWA and deployed. :white_check_mark:

  2. Examining REST endpoints currently on hold - waiting for branch omrs2msf to be merged with master/ RESTified build.

  3. Starting of Development Sprint:

  • Development shall be done in Sprints.

  • Sprint Duration: 2 weeks each

  • New Tasks created and added to Backlog

  • Kanban Board created [Link]

Current Backlog:

Sprint 1 Starts May 27, 2019 as soon as the official coding period begins! :smile:

Daily Correspondence Period:

Daily correspondence shall be done via Talk thread or Talk Message between the mentors & me - this shall discuss the tasks done for the day and issues faced (if any).

Next Weekly Call:

@maimoonak @judeniroshan @rakshir shall confer this week and setup the next weekly call. Our project’s Google Calendar scheduling is public and visible to all!

I’ve set the next call tentatively to Saturday at 11 AM CDT.

Will this be suitable? @maimoonak @judeniroshan

Hi. Here’s my blog for Week #1 . Hope you enjoy it! :slight_smile:


TODOs for Week 2 of Sprint#1 —

  • Integrate reference-app style guide & openmrs-react-components
  • Test ‘Tag’ endpoint.
  • Write API service, define DTOs (data transferable objects) and mapping service for the ‘Tag’ component.
  • Introduce Tabbed-Content in App page & route it.

Hi @maimoonak @judeniroshan ,

A few things to follow up upon:

  1. We have just completed Sprint #1 - Thread Located Here
  2. We have just started Sprint #2 - Thread Here
  3. The Blog Post for Week 2 is located here

4. The next weekly meeting -

The next weekly meeting shall be crucial for us as we would decide on topics such as -

  1. Where will we include glyphicons? Tags or Priorities?
  2. Where will we include colors? Tags?
  3. What will be our targets till Phase 1 Evaluation?

I’ve scheduled the next Weekly Meeting for Saturday, 15th June, 2019 at 11 AM CDT. Is it okay for us?

1 Like

That’s great work @rakshir. Perfect!

The time for call works for me.

1 Like

Hi @maimoonak and @judeniroshan,

PROGRESS:

Here is a 22 minute ( it’s look but interesting, I promise :stuck_out_tongue_winking_eye:) video explaining our work in GSoC till now.

OVERVIEW:

The following is an overview of our project goals, what we’ve achieved till now, and upcoming challenges and tasks.

Task Management & Breakdown Structure

Sprint Planning Overview

Upcoming Challenges & Tasks

We are currently entering Sprint #5! :smile:

Resources:

Sprint 5 Thread

GSoC Week 9 Progress Blog

1 Like

GSoC is coming to a close and we have met all our modified targets except one. And this is acting as a real blocker. I’ve got a problem that I want to discuss as well as a question regarding openmrs-react-components -

1. I’m not able to display the current user and location information in the App Header.

I’ve used the Header component from openmrs-react-components ( Header.jsx) in order to generate the header for my app, however I’m not able to display the header and location. Here’s how it looks -

As you can see, the user data and location fields are empty.

This data is read from state.openmrs.session

01ErrorReducer

I’m importing theopenmrsReducer from openmrs-react-components and setting it to an alias openmrs. This is now exported as rootReducer as you can see above.

01ErrorStore

Here’s how my Store looks.

I’m passing the store to the Header component. ( Please mind passing the store via both header and provider. It was some experiment I was doing)

However, I’m unable to see the user and location data.

2. Is there any component for Breadcrumbs in openmrs-react-components?

As you know, each OWA should have a breadcrumb UI element that shows where all the user has been.

Any Idea or help is highly appreciated :slight_smile:

c.c @judeniroshan @suthagar23 @maimoonak

This would be helpful for you -> https://github.com/openmrs/openmrs-owa-builtinreports/blob/master/app/js/components/common/Header.jsx

1 Like