OrgBook listing of public vs private data elements
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
#### Description
Work is underway to determine how to provide OneStop partners with messaging services through OrgBook.
Determine data elements that BC BN Hub Partners send / receive through the BC BN Hub.
Identify which elements are public (e.g. business name) vs which elements are private (e.g. director names).
#### Tasks
- [ ] When ticket has been created, post the ticket in RocketChat '#Operations Tasks' channel
- [ ] Add **entity** or **relationships** label to zenhub ticket
- [ ] Add 'Priority1' label to zenhub ticket
- [ ] Assign zenhub ticket to milestone: current, and place in pipeline: sprint backlog
- [ ] Reply All to IT Ops email and provide zenhub ticket number opened and which team it was assigned to
- [ ] Dev/BAs to complete work & close zenhub ticket
- [ ] Author of zenhub ticket to mark ServiceNow ticket as resolved or ask IT Ops to do so
Contributor guide
No contributing guide indexed for this repository
Research direction
No source files, tests, or code entry points are named. Start by reviewing the BC BN Hub data elements exchanged with OneStop partners and identify which are public versus private; the work is done when that classification is documented for the relevant elements.
Written by the indexing model from the issue text.
Assessment
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100