Difference between revisions of "KISS"
Jared>Admin |
Jared>Admin |
||
Line 14: | Line 14: | ||
==How We Organize Data== | ==How We Organize Data== | ||
* | *PAGE | ||
**Mediawiki | **Mediawiki | ||
* | *FILES | ||
**GitHub | **GitHub | ||
**Locally Stored | **Locally Stored | ||
* | *SERVICES | ||
**Docker | **Docker | ||
==Data Accountability== | ==Data Accountability== |
Revision as of 10:21, 5 April 2021
Keep It Super Simple:
Namespace Management
Right now data has already infiltrated every aspect of our lives and has become the most valuable and sought after asset in the world. Until recently it required an incredible amount of hardware and financial resources to be able to manage this data but due to the recent advancements of code infrastructure and cloud computing, Industry, city-sized, or globally-scaled data management systems can be created using Open Source Tools with an astonishingly short amount of time and surprisingly low costs. AI and Machine Learning are reaching stages of effectiveness that now individuals can do what used to only be possible for large corporations.
Organizations and businesses of any size will typically employ a variety of tools and services to manage marketing, social outreach, communications, accounting, human resources, file storage, inventory, logistics, etc.. Most of these services will be managed on variety of different pages with their own logins and operating ecosystems. Since these services typically are not managed in a single Namespace they are not able to interact seamlessly and then require an incredible amount of cost and time to use and maintain. Because of this incorrect management the majority of services exist simply to manage other services. People have become slaves to the services that should be serving them. This reverse of roles and all the problems and inefficiency it creates is caused by a simple misunderstanding of data management.
In order to manage Data properly we first need to understand the three kinds of Data: Data as Pages, Data as Files, and Data as Services. These three kinds of Data must be structured properly in order to achieve any desirable outcome.
Consider the human mind and body, internally the body performs incredibly complex functions without ever needing to consult the conscious mind. Breathing, Digesting, cellular growth, listening, seeing, smelling and feeling, are all things that happen automatically with zero conscious effort. All things we do externally however seem infinitely more difficult, human to human interactions like basic communication happen with so much less efficiency than the infinitely more difficult tasks that our bodies do automatically for us. The reason for this is quite simple, it's because our body operates under one namespace, one single container with a unified interaction language.
In order for our services to interact like systems within the human body they need to first be unified under a single namespace, The Page. Consistency in Namespace Management determines the integrity of data assets. To emphasize the central roles and theoretical basis of Namespace Management (NsM), we will introduce relevant tools, such as MediaWiki, and Markup Languages (HTML, YAML), as well as the rationale and the format of data outputs that will facilitate the understanding of Data Processing, Data Security, and Data Deployment.
How We Organize Data
- PAGE
- Mediawiki
- FILES
- GitHub
- Locally Stored
- SERVICES
- Docker