Hi,
I'm Spencer, and I've been doing a little work on OpenMRS for a month or
so. I'd like to get involved with this development sprint. I picked a
few issues I'd like to work on:
215: UserResource full representation throws exception in serialization
212: Concept resource should support searching for concepts by
membership in a set, or being answers to another concept
That might be about all since I'm still learning the module and OpenMRS
as I code, and I'm dividing my time with other commitments. If I have
time, this one also seems interesting.
199: Investigate and/or document POST behavior
I'll try to join the call tomorrow - when will this be discussed? The
Developer University? Design Forum? Can someone fill me in on how to join?
Thanks,
-Spencer
On 4/3/2012 12:28 PM, Friedman, Roger (CDC/CGH/DGHA) (CTR) wrote:
Dawn, Ben, Darius, Jeremy --
In going through the tasks for the sprint, I find there are some
open issues left to discuss, maybe we can start tomorrow once logic is
fully chopped:
1. Named and custom representations -- how do they differ, which will
be implemented in 1.0. I can find my stuff in RESTWS-209 but can't
find the work that the other person did with Darius.
2. Casing conventions, RESTWS-204
3. Representing self-joins, such as concept_question and concept_set,
RESTWS-190, -198, -212. Seems like on the GET call we are agreed on
answerTo, memberOf as queries and has Answers, isSet on the
default/full rep. Less consensus on whether Answers, Members
collections can be edited with POST; alternative is answerTo, memberOf
on POST, DELETE.
4. Representing subclasses -- I wrote something on this. Problem is
that same object exists at <superclass>/<uuid> and <subclass>/<uuid>.
5. Is documentation done, RESTWS-148?
That said, I think I can participate in the sprint, I think I can
do most of the following if nobody else wants them:
214: self link has wrong url
198: modifying concept_answers
196: provider resource (1.1)
212: answerTo/memberOf queries
190: hasAnswers/isSet
200: order resource
201: relation/relationship type resource
185: location attribute/location attribute type resource
178: location tag resource
Saludos, Roger
_________________________________________
To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to
[email protected] with "SIGNOFF openmrs-devel-l" in the body (not
the subject) of your e-mail.
[mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]
