**1. Purpose**
1. Automate provenance verification checks for new or existing archaeological items to ensure authentic origin, legal compliance, and improved transparency.
2. Automates cross-reference against global lost art registries, legal documents, and acquisition records—improving curatorial trust.
3. Supports curation by automatedly flagging irregularities, automating audit trails, and auto-generating compliance reports for stakeholders.
**2. Trigger Conditions**
1. New item added to the collections database.
2. Scheduled audits or collection updates.
3. Receipt of provenance paperwork via email or upload.
4. Alerts from lost/stolen artefact registries.
5. Periodic compliance re-verification cycles.
**3. Platform Variants**
1. Microsoft Power Automate
- Feature/Setting: Automate SharePoint List triggers, run approval flows, connect with compliance APIs, e.g., scheduled "When item is created" and HTTP action to Interpol API.
2. Zapier
- Feature/Setting: Automates Gmail attachments extraction and Google Sheets row insertion, then triggers webhook to museum databases.
3. UiPath
- Feature/Setting: Automates data scraping from scanned paperwork and cross-checks with Interpol Red Lists via API integration.
4. Make (Integromat)
- Feature/Setting: Automate scheduled fetch from UNESCO database, connect to museum ERPs, and notify curators.
5. Salesforce
- Feature/Setting: Use Flow Builder to automate verification tasks for new acquisitions and track all provenance updates as timeline events.
6. AWS Lambda
- Feature/Setting: Custom function automates checks against internal and external provenance APIs once new item data is pushed to S3.
7. Google Cloud Functions
- Feature/Setting: Automates email-based triggers to ingest provenance attachments and invoke verification logic by cloud function call.
8. IBM Watson Discovery
- Feature/Setting: API automates NLP-driven checks across archival documents to validate historical provenance data.
9. Trello
- Feature/Setting: Automate card creation and status change when verification workflows are initiated or completed on artefacts.
10. Box API
- Feature/Setting: Automates document uploads to specific folders and calls external automated provenance APIs on ingestion.
11. Monday.com
- Feature/Setting: Board automation triggers based on item status updates, linking to verification completion.
12. DocuSign
- Feature/Setting: Automate sending and storing digital provenance certifications and document e-signatures for compliance.
13. AirTable
- Feature/Setting: Automates record status changes when item provenance data passes verification, pulls in data from APIs.
14. Smartsheet
- Feature/Setting: Automate row addition and automated notification workflows when provenance documents are uploaded.
15. Slack
- Feature/Setting: Automated alerts in a curator channel for successful or failed provenance checks; Custom slash command for ad hoc status pulls.
16. Jira
- Feature/Setting: Automator for creating issues when provenance checks fail or require human review.
17. ServiceNow
- Feature/Setting: Workflow automation for compliance approval routing and task closure on verification complete.
18. Interpol Stolen Works of Art API
- Feature/Setting: Automated API check against international registry upon each item entry.
19. Rest API (Custom)
- Feature/Setting: Trigger automated verification on bulk upload via custom endpoint, auto-returning status per artefact.
20. Google Sheets
- Feature/Setting: Automate append of verification status and timestamped logs when external API triggers resolve.
**4. Benefits**
1. Automates manual checks, saving staff time and minimizing human error.
2. Enhances transparency and auditable provenance trails.
3. Automates regulatory compliance, reduces legal risk, and meets international standards.
4. Automating multi-source cross-referencing increases curatorial efficiency and accuracy.
5. Scalable automated solution enabling vast collection curation without manual bottlenecks.
Collections & Curation Management