waldronlab / waldronlab/BugSigDB
Add Submission Provenance Tracking
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 9
- Forks
- 9
- Avg merge
- 1h 56m
- Merged PRs (30d)
- 4
Description
Track and display the source of each submission (human curator, AI agent, bulk import) to provide transparent attribution.
Scope: Studies, Experiments, and Signatures
Requirements:
- Define semantic properties:
submittedBy,submissionAgent,submissionDate - Modify API submission endpoints to capture provenance automatically
- Display provenance metadata on Study/Experiment/Signature pages
- Include provenance fields in all exports
Use case: As AI agents submit more signatures via API, users need to know the submission source to assess confidence.
Open question for implementation: Should provenance be tracked at the page level (one set of properties per Study/Experiment/Signature), or at a more granular per-field level? Either would work, depends on what's most practical to implement and use.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the API submission endpoints and the Study, Experiment, and Signature pages and exports. First resolve whether provenance is page-level or per-field, then trace how submissions and exports are represented. Done means provenance is captured, displayed for all three resource types, and included in every export.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend-api-design, database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100