New Flags : Restricted and Internal only indicators.
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by clarifying the required metadata scope and choosing whether restricted and internal-only indicators are booleans, levels, or tags. Review the repository's semantic metadata and schema conventions; done means an agreed design that supports security and external-sharing policies, with validation and tests identified for the affected components.
Written by the indexing model from the issue text.
Description
a. In many cases, we need to set a column with a tag or indicator to specify whether the data is restricted/secured for security purposes (Example SSN or credit card number).
b. We may also need another flag to indicate whether the data is for internal use only or can be shared externally ( Item Buying price /margin or other Trade secret fields).
These indicators are essential when exposing data outside the organization and for meeting data security requirements.
Such flags can be implemented as:
- A boolean (e.g., is_restricted = TRUE/FALSE)
- An integer (e.g., security_level = 1…n)
- A string/tag (e.g., classification = 'InternalOnly' or 'ExternalAllowed')
This way, the database schema itself carries metadata about sensitivity and sharing scope, making it easier to enforce policies and comply with standards like PCI DSS, GDPR, or HIPAA and also control the data shown to outside world.
- Dominant language
- Python
- Stars
- 2.7k
- Forks
- 353
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 86
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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.
More from apache/ossie
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 52/100
Maintainers usually reply within 1 day
-
validation: field reference resolution is case-insensitive but name uniqueness is case-sensitivePossibly taken @MikeNitsenko claimed this 6 days ago. Openneeds-triage
Difficulty 5/5 Over a week Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 5/5 Over a week Newbie friendliness 25/100
apache/ossie#710 · 6 comments ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 5/5 Over a week Newbie friendliness 25/100
apache/ossie#707 · 3 comments ·
Maintainers usually reply within 1 day
Similar issues
-
integration: media_player
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
home-assistant/core#193344 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
daniel-ospina/tortoise#13607 ·
Maintainers usually reply within 1 day
-
documentation priority: medium
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 66/100
Robin-IA/Congressional-Letters-Dev#1347 ·
Maintainers usually reply within 1 day