BA Task: Fees and Fee Information re APIs
- Dominant language
- No language data
- Stars
- 0
- Forks
- 4
- Avg merge
- 1m
- Merged PRs (30d)
- 2
Description
There are (at least) two separate issues re Fees impacting Connect at this time.
1. Whether / how to include reference to the Fees page information in the updated API Terms of Use that is under review.
a. E.g. include the URL for the page - is this standard practice for a ToU from a legal standpoint?
2. On the Fees page itself https://www.bcregistry.gov.bc.ca/en-CA/product-fees, there are a number of questions needing resolution:
a. Who is the current target audience for the Fees page? Is it all Modernized users (i.e. those using the BC Registries UI application? Or is it also aimed at API users? What about Government partners who are API users?
b. Possible introductory information / para explaining the page;
c. What Fees apply to PROD API Users
d. What Fees apply to Sandbox API Users
e. What Fees apply to Govt API users - does this same page apply to them?
f. Tombstone data will be No Fee - but where is this stated.
Reach out to Pay team (John / Patty) on some of the above.
Contributor guide
Research direction
Start with the Fees page at https://www.bcregistry.gov.bc.ca/en-CA/product-fees and the updated API Terms of Use under review. Confirm the intended audiences and fee treatment for PROD, Sandbox, Government API users, and tombstone data with the Pay team. Done means the audience, introductory guidance, applicable fees, and Terms of Use reference are resolved and documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100