Scribd
Upload
241 views

Veracross Filemaker

The document discusses several systems that currently integrate with or pull data from a Filemaker database, and how they may integrate with Veracross instead. It describes: 1) The transport system currently pulls student, family, staff, and contact data from Filemaker tables. To replicate this in Veracross, the API would need to import key fields from relevant tables. 2) The SLD system similarly pulls key data like student IDs, names, and medical information. This functionality would need to be maintained through Veracross API imports. 3) The laptop reservation system links classes, teachers and hardware. It would need API access to tables of teachers, courses, and hardware attributes to function as currently. 4

Uploaded by

Danny Dawson
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
241 views

Veracross Filemaker

The document discusses several systems that currently integrate with or pull data from a Filemaker database, and how they may integrate with Veracross instead. It describes: 1) The transport system currently pulls student, family, staff, and contact data from Filemaker tables. To replicate this in Veracross, the API would need to import key fields from relevant tables. 2) The SLD system similarly pulls key data like student IDs, names, and medical information. This functionality would need to be maintained through Veracross API imports. 3) The laptop reservation system links classes, teachers and hardware. It would need API access to tables of teachers, courses, and hardware attributes to function as currently. 4

Uploaded by

Danny Dawson
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Veracross Filemaker

Transport The current transport database pulls data from the following tables: Parents, Families, Telephone Numbers, Email Addresses Students and Staff. To achieve the functionality that we currently have the API would need to be able allow the import of: Student ID, Student First, Student Last, Homeroom, Family ID, Grade from the student/people? Table in Veracross. Parent ID, Parent First, Parent Last, Family ID, Family Salutation, Email, Telephone and Address data from the parent/people? Table in Veracross Staff ID, Staff First, Staff Last from the staff/people table in Veracross.

The staff data is primarily used to link the driver record in the staff db to an interface in transport so that the transport manager can see that the HR office has carried out list 99 police checks. There are also times when the transport department assigns teachers to buses as bus riders in the same way as students are assigned to busses.
As well as pulling data the current system pushes bus data to other areas of the system. The After school programs currently enter the time a student would require a bus on a given day related to there after school commitments, the transport department can see this and then assign a specific bus to the student based on this time. When the bus is assigned to the student that bus appears in the After School system so that lists can be produced of students in activities with there bus information. The Lower school also produces attendance lists that show bus information from the transport database. If we wish to push data from transport into Veracross I do not believe that the best way to do this would be via an API. The most efficient way would be able to connect and push data into the tables of Veracross via a SQL connection although this raises security of data issues and would be dependent on Veracross being comfortable with this level of interaction with the back-end of there system.

SLD
The current SLD Database pulls data from the following tables. Register (current students), Parents, Parents Telephones, Parent Emails and Student Medical. To achieve the functionality that we currently have the API would need to be able allow the import of: Student ID, Student First, Student Last, Homeroom, Family ID, Grade from the student/people? Table in Veracross. Parent ID, Parent First, Parent Last, Family ID, Family Salutation, Email, Telephone and Address data from the parent/people? Table in Veracross. Medical Data As the medical part of the Veracross Database is being created there will be no API as yet but if we want to maintain this functionality then perhaps it could be part of the development of the new module. The SLD has read access to this data in their system and it currently details conditions and medications for the student population. The key field that joins the Medical information to the SLD database is the student ID.

Laptop Reservations
The laptop reservation system is divisionally based and is linked to classes and teachers. To build the system with the current functionality you would need the following tables of data, which would need to be populated by API queries. Teachers: A table of each Teacher primarily with teacher ID, First name, Last name. Courses: A table of courses with Course ID, Course Title, Term, Teacher ID Schema: We currently have a table that has each day of the school year with fields containing, date, term, division and number (cycle days 1-8) - I do not believe that an API exists in Veracross to pull this data into Filemaker Hardware: A table of the Laptops that are available to book with Serial number, Tag Number, Grouping (attribute fields that indicate the platform (Mac / PC) and the Division (HS / MS)) I do not believe that an API exists in Veracross to pull this data into Filemaker

Some other systems?


There are a number of other systems that use data provided by Filemaker. The majority of these are relatively simple CSV uploads of core student, parent and staff data. The specific functionality that Filemaker provides is the ability to script the process. The Destiny Library software is populated each night by a three-stage process that runs on a server. A batch process triggers a Filemaker script that queries the databases and exports 3 csv files into a specific folder. A batch process then places these files on the library server and a third batch process uploads them into destiny. The file itself contains basic data on all possible users of the library (Students, Parents and Staff). If we were to continue to manage this system in this way Filemaker would need to be able to bring in data from Veracross via the APIs and then run the process in the same way. I believe that the APIs are already in place to achieve this. The GroupCall SMS system runs in a very similar way the data that is sent to group call is parent, staff and student mobile phone numbers. Again I believe the APIs are in place to do this. TDSI Security. This requires 4 CSV files that are uploaded into the system via a local application. The creation of the CSV files is managed by running a Filemaker script that finds any unprocessed ID cards and exports the CSV files from that set of records, The first column Of each uploads contains a sql statement that is calculated in Filemaker and used by the TDSI system. Finalsite. I would expect all Finalsite uploads to come directly from Veracross

Veracross Moodle
Again I would hope that this will be easier with Veracross and the process of exporting data and uploading it into Moodle will be managed exclusively by Veracross.

Danny Dawson 8.9.2009

You might also like