infra/otc-metadata
16
0
Fork 13
Code Issues 2 Pull Requests 1 Packages Releases Wiki Activity

small fix
Some checks are pending
gl/check check status: pending (a7743e4c38792ac1d18561e1b08b826b6c702a15)
Details

Browse Source
This commit is contained in:
Tino Schreiber 2023-05-12 07:18:33 +00:00
parent 0c93fa1e4a
commit a7743e4c38
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.rst
View File

@ -37,7 +37,9 @@ which can be compared with database tables in a relational database.
* documents: contains the information about every single document and its type * documents: contains the information about every single document and its type
like umn, api-ref etc. like umn, api-ref etc.
* service category: contains the keyword and title of the service category * service category: contains the keyword and title of the service category
* services: contains the repository information about the internal (Gitea) and * services: contains the repository information about the internal (Gitea) and
external location (GitHub) and all the necessary parameters of the service external location (GitHub) and all the necessary parameters of the service
itself itself
@ -49,5 +51,5 @@ For the :code:`services` table
the key is :code:`service_type` which has the foreign key in the the key is :code:`service_type` which has the foreign key in the
:code:`documents` table. So a service can have multiple documents and each :code:`documents` table. So a service can have multiple documents and each
document can only be linked to one service. document can only be linked to one service.
The key :code:`service_category` table is :code:`name`of the service category The key :code:`service_category` table is :code:`name` of the service category
which is then used in the :code:`services` table as foreign key. which is then used in the :code:`services` table as foreign key.