Monthly Archives: February 2014

Week 2: 3 February 2014

[IRC]

The IRC activity that we did in class was awkward to say the least. For starters, before going into further detail, I did not know people still used IRC in today’s age of the internet. It seems that it is extremely dated and only suited for some of the “hardcore” or old-school crowd that are stuck in the old ways. After downloading a few clients (experimenting with some proved to be more difficult or hard to navigate) I landed on one that was recommended to me by Brian Gibson — HexChat. After setting up the initial server and identity for myself, I connected pretty easily.

The whole conversation that took place afterwards was silently done inside the IRC. It gave me a first glimpse of how to use it and to speak my thoughts clearly via an online forum. The in-class lack of speaking was a little weird, but the exercise was meant to show us how to use it in case we could not meet for class. All in all, I think it was valuable even though I thought the method of doing online meetings was a little dated.

 

[Readings]

The readings for this week were a good statement to me personally as to how I could contribute more to the project. I do not believe I have anything much higher than an average programming level, nor do I have extensive knowledge into other languages and tools other than what I’ve used during my major progress at WSU. So joining this open source project seemed a little daunting. I did like to see that there were tons of other ways to contribute (I’m more keen to the documentation and bug tracking part). Some of the examples I could tell were a little “out there” in terms of how they were actually going to help, but I can see the end result of it all.

Reading about the bug tracking methods and etiquette was not 100% new information, seeing as I have worked in an environment before where bugs were coming up from clients and we were helping resolve them. For a programming aspect, though, it is applicable in almost the same way. I think the OpenMRS bug tracking feature is well developed (it has to be at the scale it is at this point) and should be easy to pick up on as bug tracking becomes part of the assignment.

From the blog slykrysis » cs-wsu by slykrysis and used with permission of the author. All other rights reserved by the author.

Week Four

For something that should be fairly easy and straightforward, getting the OpenMRS started was much more involved that it should have been. For one thing, the installer did not work at all, so I did the manual installation instead. Getting the maven and mysql aspects up and running were easy using Homebrew, and we had already cloned the git repository so that was easy. I needed to download the java 7 SDK, and then compiled everything. However, when i compiled and started the web app, I was missing the /var/lib/OpenMRS/openmrs-runtime.properties file, and as of now have not been able to figure out where it is and why it is missing from the git repository.

From the blog ckelley6 » CS401 by ckelley6 and used with permission of the author. All other rights reserved by the author.

Week Three – Three Issues

The introductory bugs seemed like a good way of learning and contributing to the project. I think that the ticket creation ticket is good, because it will help learn about using the bug system, and the icon bug seems like it would be an easy fix that would make the application much easier to use for computer illiterate people.

From the blog ckelley6 » CS401 by ckelley6 and used with permission of the author. All other rights reserved by the author.

Week Three

I thought that the git activity served as a simple thing to learn how to better use a tool that will come in handy later on. On the other hand, the videos did not seem to be highly useful as they mostly just stated fairly obvious things about git and SCM as a whole. The wiki editing seemed to be fairly easy, but made me think of all the work that must go into maintaining a wiki with lots of information in it. The issue tracker activity was interesting to me because we use bug tracking at work, and a lot of the information was similar. However, this seemed to be much clunkier than Accurev, the program we use.

From the blog ckelley6 » CS401 by ckelley6 and used with permission of the author. All other rights reserved by the author.

Week 3 reading OpenMRS

The OpenMRS can improve the health care quality, it can reduce many medical errors . The OpenMRS is very commonly  for the patient-centric medical. OpenMRS has become the largest health IT project on the planet. OpenMRS community is developed at many countries around the world. Joining in the OpenMRS community is very helpful, it also help you to solve many different problem as you can comment or mail to ask your question with any thing you still doubt. The more you talk to the OpenMRS community group the more you earn your new technology knowledge .

Wiki editing is more fun and interest, on the wiki page we can share the experience from what we learn in the class. Otherwise,  we can consult the classmate’s idea how they will do  project.

The three issues were chosen:

1. TRUCK- 324

2.TRUCK-309

3.STAND-19

From the blog herangoc » cs@worcester by emtrieu and used with permission of the author. All other rights reserved by the author.

SYSTEM SETUP

Initially I went forward setting up my machine which runs on Windows 8 OS. After running into issues with the JDK installing properly. I decided to go ahead and install Ubuntu on VM Ware. I’m glad I made this decision early because I feel as though I saved myself a lot of headaches. First of all it was nice that Ubuntu made it simple to update to java and javac 1.0.7.0_04, so after I installed that I went ahead and installed MySQL. Again I was pleased to find that Ubuntu came pre-packaged with MySQL 5.5 which again made installation a breeze just set up username and password and I was good to go with that. Next came installing the SDK for OpenMRS. This is where I hit my first snag. The version that was in the OpenMRS Users Guide OpenMRS 1.0.6 didn’t play well with the version of javac I had installed, so I did some searching and found a version new OpenMRS SDK that was 1.0.7. Once I unzipped it and created a folder in the /var/lib/ called OpenMRS it automatically created a file called openmrs-runtime.properties along with other files. After that was set up I then turned to install Maven. Once Maven was installed. I went to install Github, once again the version of Github on the OpenMRS Guide didn’t compile correctly on my machine so I searched and found Git version 1.7.9.5. I then cloned the openmrs-core repository on GitHub using my Git client with the command git clone https://github.com/openmrs/openmrs-core.git. I then changed directories to openmrs-core by cd \openmrs-core where I ran a clean build by the mvn clean install command. I had a successful build with:
[INFO] Reactor Summary:
[INFO] ————————————————————————
[INFO] OpenMRS ……………………………………….. SUCCESS [16.781s]
[INFO] openmrs-tools ………………………………….. SUCCESS [6.550s]
[INFO] openmrs-test …………………………………… SUCCESS [1.312s]
[INFO] openmrs-api ……………………………………. SUCCESS [3:16.633s]
[INFO] openmrs-web ……………………………………. SUCCESS [1:20.083s]
[INFO] openmrs-webapp …………………………………. SUCCESS [35.861s]
[INFO] openmrs-release-test ……………………………. SUCCESS [33.070s]
[INFO] ————————————————————————
[INFO] ————————————————————————
[INFO] BUILD SUCCESSFUL
[INFO] ————————————————————————
[INFO] Total time: 6 minutes 11 seconds
[INFO] Finished at: Fri Feb 21 13:07:01 PST 2014
[INFO] Final Memory: 68M/174M
[INFO] ————————————————————————

After I ran the build I again switched directories to webapp by cd /opennmrs-core/webapp. Once in the webapp directory I ran the command mvn jetty:run. Upon running that command I was able to access OpenMRS using the url http://localhost:8080/openmrs/index.htm not the url given in the Developers Guide. Once I completed the required the initial setup I was good to go! All in all I think the entire setup process went fairly smoothly, but I do think that the Developer’s Guide itself needs some updating. Mainly with the types of versions that play nice with each other, and give a complete localhost address.

Till next time,

Matthew Lopatka

From the blog mlopatka by matthewlopatka and used with permission of the author. All other rights reserved by the author.

Wiki & Git are FUN!

The third week of the semester has been very busy. Let’s start with the wiki editing that was started in class. This is the first time I have to edit a wiki. It was fun and easy to learn how to add and modify content. What I like about the wiki application is its simplicity, which allows any user to contribute text without being a web designer.

My wiki profile has information about the Issue Tracker Activity. This activity was useful in a way that I can get familiar with the OpenMRS Issue Tracker system, which is a system that allows browsing and filtering bugs. In this activity not only learned to browse and filter issues, but I also learned to find reports based on a specific project.

The second part of the assignment was the Git Videos and the tutorial, which gave me an insight of what Git is and how it works. Git is a Version Control System (VCS) with capability to keep track the history of every file, and changes made by a team member who is working or collaborating on a single project. VCS allows to revert files back to a previous state, revert the entire project, review changes made over time, see who last modified something that might be causing a problem, who introduced an issue and when, etc.

In summary, some features that Git provides are:

  • Configuration: Free download and installation; fast and easy setup.
  • Fast: Nearly all operations are performed locally (on local disk).
  • Distributed Version Control: if any server dies, any of the client repositories can be copied back up to the server to restore it.
  • Team Centric: Allows group of contributor working simultaneously within the same project.
  • Integrity: Contributor can’t lose information in transit or get file corruption without Git being able to detect it.
  • Merging Capability: Git is flexible when more than one user’s work needs to be brought together.
  • Opt in: You decide on which projects to participate.
  • Open Software: Let people offer contributions.
  • Backup: Every user has a full backup of all data. 

Finally, this week I went through the selection of 3 tickets within the issue tracker. I am very excited to work on projects related to database.

From the blog Naty Zelaya » CS@Worcester by natyzelaya and used with permission of the author. All other rights reserved by the author.

Wiki Editing, Issue Tracker Activity, Git Videos and Tutorials and Selecting 3 Issues

Wiki Editing

The Wiki Editing I felt was a great learning experience. I’ve never had my own personal wiki page so that’s pretty neat. I like the fact that I now have a page that I can store, edit and share information with others is very powerful. I often use Wiki to look up everything from types of dinosaur’s to answer my son’s questions, to computer science questions for my own use. I’m not use to putting information out there for the world to access, I’m one of those people who feel as though once you put something out there it’s out there forever. I imagine having this wiki page will break me out of my shell!

Issue Tracker Activity

The Issue Tracker Activity was fun. It really gave you a lot of information in a single activity. This activity was definitely one of my favorites. Although I have some previous experience with other types of Issue Trackers it was a great refresher. Having you have us list all of the different definitions for the key terms really made me familiarize myself with the Issue Navigator itself. Part 2 of the exercise was just as helpful for understanding how OpenMRS sets up its projects in their trunk. It was fantastically easy to navigate thought their interface to find the information that was requested. Everything seemed to be in order and the layout of the trunks information was obviously thought out.

Git Videos and Tutorials

The Git Videos and Tutorials were very informative and useful. One of my favorite features described on the Git video was Git’s ability to operate completely off-line. I think that’s amazing coming from Tortoise SVN where you would need a network connection to do any pulls, forks, merges or commits. I was also surprised that Git has been around for several years. I guess over that time it has been able to implement useful features and easy commands that make it a leader in version control software today. I like the fact that the software is simple enough to navigate and operate for the novice developer, but has the capabilities to conform to a more advanced developer. I also like the fact that Git follows content and not the files themselves, Git actually will follow the code through the files and that’s pretty neat!
The Git Challenge was fun, I earned my badge! I enjoyed the format of the exercise. Being able to see the Git commands and type them simultaneously and then observe the output was very helpful in grasping the basics of Git. I believe I will continue to go through the tutorials when I have free time.

Selecting three issues

TRUNK-367
New Feature
Create a German messages.properties translation file
Description – It would be convenient to have a German translation of the messages.properties file.
Why this ticket? I’ve worked with translation tools such as LocBaml and Redpin for .Net applications in the past so I think this would be a great way to get my feet wet.

TRUNK-15
New Feature
Saving the same name more than once should not be allowed.
Description – I Can save Relationship Types, Concept Classes, Patient Identifier Types, Field Types, Drug Order Types, with the same name, any number of times. I guess this behavior is not intended.
Why this ticket? It seems like a bit of redundancy that could be cleaned up. Maybe having multiple name saves could lead to conflicts.

REPORT-517
Improvement
Description – There have been many, many confused users who cannot get their reports to run because their scheduler username and password global property is not set to a valid user with appropriate credentials.
We should check this on the run report page and ensure that such a valid user exists before allowing a user to run any report. If the credentials are invalid, we should provide a clear error / warning, and provide instructions for the administrator to update these settings.
Why this ticket? I think with this improvement the user would at least get an immediate warning that invalid credentials are being entered, leading to less confusion and time loss.

From the blog mlopatka by matthewlopatka and used with permission of the author. All other rights reserved by the author.

Week 3

Wiki editing is always fun, I have done some wiki editing in the past however every wiki is a bit different. The issue tracker activity was fun, I have never used Jira before but I think it is a very advanced issue tracker. There are so many tools with this issue tracker. I can see a small learning curve with Jira but it will be very powerful. The github activity was very informative, I have used git in the past so going through the git tutorial again was a good refresher. 

From the blog tbruceblog » cs401 by tbruce731 and used with permission of the author. All other rights reserved by the author.

CS-401 Week 3

During the third week of the course, we did some work on the wiki page. we created our own wiki page and edited it with our information. We created a link of our page to the student page of the course, where all students can find one another.

Another exciting activity we did was the issue/bug tracker activity. This activity gave us first hand experience with the issue tracker and how to analyze the report of bugs or any issue. We got introduced to the many different parts of the issue report and various symbols of what the issue status is or when it was modified.

For assignments, we watched a couple of videos concerning the github  utility. The videos went over the introduction and importance of the git tool. It shows how easier it is to work on the same file with many others, and how to bring the ideas together. The video also went into how to install, configure, and use the git repository.

*******************************

The three issues I find interest in working on

Report-420: the issue is that it display a list of report using data.

Trunk-15: the issue is that saving the same name more then once should not be allowed.

Trunk-309: the issue here is to add a better Javadoc comments to services.

From the blog ~~~ACordor Blog~~~~ » CS@Worcester by juwee05 and used with permission of the author. All other rights reserved by the author.