On Sun, Feb 26, 2012 at 11:21 AM, Gour <[email protected]> wrote:
> On Sun, 26 Feb 2012 09:25:17 -0400
> Chris Peachment <[email protected]> wrote:
>
>> It looks to me like you could add a new field to the 'ticket' table,
>
>> The missing part is some way to pass the patient id to the report so
>> that it selects only tickets for the given patient.
>
>> You might need to hack the report menu source code to permit entry of
>> one (or more) parameters when the report is selected.
>
> Huh...my C skills are rusty and I hoped I could do without surgery
> 'cause otherwise tweaking Roundup tracker might be easisier solution.
>
> Let's see if there is some other idea.

I am reasonably sure it can be done with out "C surgery". (However, a
proper search feature for tickets should be added to Fossil.)

Use Fossil wiki pages for the "master" patient files. (the "built in"
wiki pages).

In a Fossil wiki page, a ticket id enclosed between [ and ] will
function as a link to the ticket. (This also works with "embedded
document" wiki pages, but updating embedded document pages with the
Fossil UI is not (yet) possible.)

Using some combination of TH1 and Javascript, the link to a new ticket
can be appended to a wiki, automatically, when the ticket is
created.Actually, this would be done in View Ticket right after the
ticket is forst entered. At that point, the ticket status is New. At
that point, Fossil performs an automatic View Ticket. This is where
the extra processing takes place. A combination of TH1 and Javascript
would see that the status is New and display a Confirm button, along
with a message instructing the user to verify the entered information,
then clinck on Confirm. Javascript would then subimt both a HTTP
request to append [ticketID] to the patient's wiki page, and a HTTP
request to update the ticket status to something other than New.

(probably necessary for the View Ticket of a New ticket to include the
raw wiki page content in a hidden text area that the Javascript would
then append to and submit much like editing a wiki in the Fossil UI.)
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to