digitalbazaar / digitalbazaar/bedrock-tokenization
Add feature for optionally recording fraud / authentic scores for registered documents
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 2
- Avg merge
- 5m
- Merged PRs (30d)
- 1
Description
Additional registration information should be able to be tracked for registered documents such as how likely the document is to be an authentic (which is not the same as how likely it is to be related to a particular entity that may have presented it).
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
The issue does not identify files, tests, or an entry point. Start by reviewing how registered documents and their existing registration information are represented, then clarify the meaning, optionality, storage, and completion criteria for authentic and fraud scores before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100