1. Investigation Phase (#2): * What software do we have access to? * https://github.com/HeritageBridge/HeritageBridge * https://github.com/GlobalHeritageFund/amal-ios * https://github.com/GlobalHeritageFund/amal-android * https://github.com/archesproject/arches * Get it running on local system (#3) * Understand how HerBridge links AMAL to ARCHES * What has changed between ARCHES v3 and v7 * https://arches.readthedocs.io/en/stable/ * https://arches.readthedocs.io/en/3.1/ * UPDATE: Repository contains release markdown files, that contain version update information (https://github.com/archesproject/arches/tree/stable/7.5.3/releases) * What needs to be changed about the HerBridge software? (#2) * Retrieve credentials for ARCHES instance to develop with (#3) * Develop with a local instance, or with the EAMENA server? * https://www.classics.ox.ac.uk/eamena-endangered-archaeology-middle-east-and-north-africa 2. Development Phase (#4) * Outline changes to be made to HerBridge & confirm * Make changes to HerBridge * Detail here TBC when better understood 3. Testing (#5) * Determine scope of required testing * Will current unit testing require updating? 4. Deployment (#6) * We still need to determine our role in deployment. 5. Bugfixes (iteration) (#7) Update meeting scheduled every 2 weeks
Update meeting scheduled every 2 weeks