Overview
My API
System Designs
Dienstleistungen
Kontakt
Energieausgleich
Ansprechpartner
Impressum
Prompt for the
GeodatensatzApp
Please create a React-JS application for the GeodatensatzModule. The application has to offer the following views for the user interface: 1. GeodatensatzView 2. OpenDataLizenzView 3. OpenDataVeroeffentlichungView The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 3 views are defined below. 1. The GeodatensatzView must contain the following fields: - name: Aktualisierungszyklus type: STRING - name: Beschreibung type: STRING - name: Datensatzkategorie type: Datensatzkategorie - name: ErzeugtAm type: DATE - name: Kurzname type: STRING - name: Name type: STRING - name: Raumbezugssystem type: Raumbezugssystem - name: VerantwortlicheOrganisationseinheit type: Organisationseinheit The data source for the [Datensatzkategorie] select control should be loaded from the relative URL: "/OrganisationseinheitService/datensatzkategorie" (HTTP-GET) The data source for the [Raumbezugssystem] select control should be loaded from the relative URL: "/RaumbezugssystemService/raumbezugssystem" (HTTP-GET) The data source for the [VerantwortlicheOrganisationseinheit] select control should be loaded from the relative URL: "/OrganisationseinheitService/organisationseinheit" (HTTP-GET) An existing Geodatensatz entity should be loaded from the relative URL: "/GeodatensatzService/geodatensatz/{id}" (HTTP-GET) If a new Geodatensatz entity has been created, the new entity should be posted to the relative URL: "/GeodatensatzService/geodatensatz" (HTTP-POST) If an existing Geodatensatz entity has been updated, the modified entity should be sent to the relative URL: "/GeodatensatzService/geodatensatz/{id}" (HTTP-PUT) If an existing Geodatensatz entity has to be deleted, the following relative URL should be called: "/GeodatensatzService/geodatensatz/{id}" (HTTP-DELETE) Add a HTML table to the view with the following Zugriffsprotokoll columns: - column: Geodatensatz - column: ZugriffAm - column: ClientIp - column: Kartendienst - column: Benutzerkonto - column: Aktion The table should have the title "Zugriffsprotokolls" und the data must be loaded from the server with the following relative URL: "/KartendienstService/zugriffsprotokoll/geodatensatz/{id}" Add a HTML table to the view with the following OpenDataVeroeffentlichung columns: - column: OpenDataLizenz - column: Geodatensatz - column: VeroeffentlichtAm - column: ErzeugtAm - column: Titel - column: PortalUrl - column: AktualisiertAm The table should have the title "OpenDataVeroeffentlichungs" und the data must be loaded from the server with the following relative URL: "/GeodatensatzService/opendataveroeffentlichung/geodatensatz/{id}" Add a HTML table to the view with the following Kartendienst columns: - column: ErzeugtAm - column: Url - column: Geodatensatz - column: Oeffentlich - column: Diensttyp - column: Name - column: Version The table should have the title "Kartendiensts" und the data must be loaded from the server with the following relative URL: "/KartendienstService/kartendienst/geodatensatz/{id}" Add a HTML table to the view with the following CopernicusDatensatzVerknuepfung columns: - column: Geodatensatz - column: ErzeugtAm - column: CopernicusProdukt - column: Beschreibung The table should have the title "CopernicusDatensatzVerknuepfungs" und the data must be loaded from the server with the following relative URL: "/CopernicusProduktService/copernicusdatensatzverknuepfung/geodatensatz/{id}" 2. The OpenDataLizenzView must contain the following fields: - name: Beschreibung type: STRING - name: Code type: STRING - name: ErzeugtAm type: DATE - name: Name type: STRING - name: Url type: STRING An existing OpenDataLizenz entity should be loaded from the relative URL: "/GeodatensatzService/opendatalizenz/{id}" (HTTP-GET) If a new OpenDataLizenz entity has been created, the new entity should be posted to the relative URL: "/GeodatensatzService/opendatalizenz" (HTTP-POST) If an existing OpenDataLizenz entity has been updated, the modified entity should be sent to the relative URL: "/GeodatensatzService/opendatalizenz/{id}" (HTTP-PUT) If an existing OpenDataLizenz entity has to be deleted, the following relative URL should be called: "/GeodatensatzService/opendatalizenz/{id}" (HTTP-DELETE) Add a HTML table to the view with the following OpenDataVeroeffentlichung columns: - column: OpenDataLizenz - column: Geodatensatz - column: VeroeffentlichtAm - column: ErzeugtAm - column: Titel - column: PortalUrl - column: AktualisiertAm The table should have the title "OpenDataVeroeffentlichungs" und the data must be loaded from the server with the following relative URL: "/GeodatensatzService/opendataveroeffentlichung/opendatalizenz/{id}" 3. The OpenDataVeroeffentlichungView must contain the following fields: - name: AktualisiertAm type: DATE - name: ErzeugtAm type: DATE - name: Geodatensatz type: Geodatensatz - name: OpenDataLizenz type: OpenDataLizenz - name: PortalUrl type: STRING - name: Titel type: STRING - name: VeroeffentlichtAm type: DATE The data source for the [Geodatensatz] select control should be loaded from the relative URL: "/GeodatensatzService/geodatensatz" (HTTP-GET) The data source for the [OpenDataLizenz] select control should be loaded from the relative URL: "/GeodatensatzService/opendatalizenz" (HTTP-GET) An existing OpenDataVeroeffentlichung entity should be loaded from the relative URL: "/GeodatensatzService/opendataveroeffentlichung/{id}" (HTTP-GET) If a new OpenDataVeroeffentlichung entity has been created, the new entity should be posted to the relative URL: "/GeodatensatzService/opendataveroeffentlichung" (HTTP-POST) If an existing OpenDataVeroeffentlichung entity has been updated, the modified entity should be sent to the relative URL: "/GeodatensatzService/opendataveroeffentlichung/{id}" (HTTP-PUT) If an existing OpenDataVeroeffentlichung entity has to be deleted, the following relative URL should be called: "/GeodatensatzService/opendataveroeffentlichung/{id}" (HTTP-DELETE)
Copy prompt
Overview
My API
System Designs
Dienstleistungen
Kontakt
Energieausgleich
Ansprechpartner
Impressum