Python–FileMaker Data Integration
Budget: $15 – $25 USD
I want a clean, well-documented Python layer that talks directly to my existing FileMaker solution. The goal is to let my scripts read, write, and update records that contain a mix of text, numbers, and other field types without disrupting daily use of the database.
This is revamping an existing connection between law firm authorized user and external web database.
Connection method is flexible—FileMaker Data API, XML Gateway, or ODBC are all acceptable as long as the final code is reliable, secure, and keeps the FileMaker file schema untouched. Because several people will eventually call these functions, I also need a simple role system inside the Python code (e.g., admin, editor, viewer) that maps to FileMaker credentials and cleanly blocks unauthorized actions.
Please deliver:
• A reusable Python module (Python 3.9+) with functions for create, read, update, delete.
• Configuration file or section for server URL, database name, and role-based credentials.
• A concise README showing installation steps, example calls, and how to extend the role logic.
• Brief comments in the code explaining each significant step so future developers can pick it up fast.
Additional Scope:
• Fixing issues with PDF downloads from the court website.
• Adding functionality to upload PDFs to the court filing portal.
• Creating thorough documentation for future developers.
• Supporting additional features as the project evolves.
This is revamping an existing connection between law firm authorized user and external web database.
Connection method is flexible—FileMaker Data API, XML Gateway, or ODBC are all acceptable as long as the final code is reliable, secure, and keeps the FileMaker file schema untouched. Because several people will eventually call these functions, I also need a simple role system inside the Python code (e.g., admin, editor, viewer) that maps to FileMaker credentials and cleanly blocks unauthorized actions.
Please deliver:
• A reusable Python module (Python 3.9+) with functions for create, read, update, delete.
• Configuration file or section for server URL, database name, and role-based credentials.
• A concise README showing installation steps, example calls, and how to extend the role logic.
• Brief comments in the code explaining each significant step so future developers can pick it up fast.
Additional Scope:
• Fixing issues with PDF downloads from the court website.
• Adding functionality to upload PDFs to the court filing portal.
• Creating thorough documentation for future developers.
• Supporting additional features as the project evolves.
Related categories:
Python
Software Architecture
MySQL
FileMaker
Software Development
Documentation
API Development
Data Management