Pages containing 'Fileman'
In its 1.1 release, FMQL will move its JSON format over to JSON-LD. This form of JSON provides a straightforward JSON with rigorous semantics, something key for VistA data with its large and powerful data model.
I am please to announce that I finished writing a Fileman tutorial for programming students that I promised Luis Ibañez. Here it is.
Thank you Luis for the impetus, and sorry it took so long.
FLAP Worker Bee
We got more reader feedback (thank you!), so here is an updated version of the Getting Started Manual. Hopefully this is also the final version.
We are now working on the Security Manual, and hope to have it available by the end of February.
We will use the new peer review checklist to walk through peer review for FileMan 22.2 in the OTJ. Peer review checklist is at:
Update: We had a very successful consensus review of Fileman 22.2 during yesterday's meeting. Based on the meeting, we have the following two actions that need to be investigated, after which we will submit a recommendation via the peer review:
Based on reader feedback, we made a few changes to the Getting Started Manual. Here is the updated version.
This is the Getting Started Manual for Fileman 22.2 in PDF format. We are working on an HTML version, and will link to it when it is complete.
Detailed updates to Visual Cross Reference Documentation (http://code.osehra.org/dox/index.html)
By following the installation instruction of the Fileman 22.2 submission in OSEHRA Technique Journel (http://code.osehra.org/journal/browse/publication/27), we install Fileman 22.2 sucessfully on a VistA instance based on FOIA 082412 release. Routine changes are extracted and imported into VistA-FOIA git repository based on FOIA 082412. The difference between Fileman 22.2 and FOIA 082412 can be view directly via github:
Context: been mailing with Sam about a code convergence call and here are some data-centric FileMan issues I'd like to bring up.
All in all, I'd like FileMan to be fully self-describing and enforcing so that its data is easier to model and mine. I don't want to have to do ANY data rework in an outside data store.
1. the three types of multiple: we need to distinguish/define these formally