Difference between revisions of "MCatalog/Output"

From PKC
Jump to navigation Jump to search
Line 5: Line 5:
[[MCatalog/Output|Click on this link to see details]].
[[MCatalog/Output|Click on this link to see details]].
<noinclude>
<noinclude>
=Detailed Description=
# A set of web-base [[mCatalog application]]s that utilizes [[Ethereum-based blockchain]] to read and write [[LKPP]] administrated product/service catalog data.
# A set of web-base [[mCatalog application]]s that utilizes [[Ethereum-based blockchain]] to read and write [[LKPP]] administrated product/service catalog data.
# A documentation framework based on [[PKC]] that document the developmental and data verification/validation process of the above mentioned [[mCatalog application]]s.
# A documentation framework based on [[PKC]] that document the developmental and data verification/validation process of the above mentioned [[mCatalog application]]s.

Revision as of 10:14, 4 June 2022

  1. A set of web-base mCatalog applications .
  2. A documentation framework based on PKC .
  3. A data backup and restore procedure.
  4. A user authentication and authorization service to manage the overall data asset. (Content data and source code).

Click on this link to see details.

Detailed Description

  1. A set of web-base mCatalog applications that utilizes Ethereum-based blockchain to read and write LKPP administrated product/service catalog data.
  2. A documentation framework based on PKC that document the developmental and data verification/validation process of the above mentioned mCatalog applications.
  3. A data backup and restore procedure that packages the developmental data and source code content, so that LKPP can constantly read and write data and source code along with this developmental team.
  4. An open-source user authentication and authorization service (Keycloak) that is integrated with PKC and administrated by LKPP to manage the overall data asset. (Content data and source code).