OZG implementation

State of implementation of the Online Access Act (OZG) in Schleswig-Holstein. ## Fields — ‘lock’ — project-side unique identifier for administrative performance — ‘entry entry’ — Was the performance (first) not included in the OZG catalogue and was subsequently identified by SH? — ‘catalogue_LeiKaSchluessel’ — corresponds to OZG catalogue meaning — ‘catalogue_LeiKaTyp’ — corresponds to OZG catalogue meaning — ‘catalogue_LeiKaLeistung’ — largely corresponds to OZG catalogue content; In case of doubt, however, the common name in SH is entered here. — ‘Catalog_OZGThemenfeld’ — Matches OZG Catalog Meaning — ‘catalogue_OZG’ — Conforms to OZG Catalog Importance — ‘catalogue_OZGPerformance’ — corresponds to OZG catalogue meaning — ‘catalogue_legal basis’ — largely corresponds to OZG catalogue content; In case of doubt, however, the legal basis in SH is entered here. — ‘catalogue_Gesetzeskuerzel’ — largely corresponds to OZG catalogue content; In case of doubt, however, the abbreviations commonly used in SH are entered here. — ‘catalogue_Top100Wirtschaftdetails’ — Conforms to OZG Catalog Importance — ‘Catalog_Top100BuergerDescription’ — Conforms to OZG Catalog Meaning — ‘Catalog_Behoerdenrufnummer115’ — Conforms to OZG Catalog Importance — ‘Catalog_SDG1Relevance’ — Conforms to OZG Catalog Meaning — ‘Catalog_SDG2Relevance’ — Conforms to OZG Catalog Meaning — ‘catalogue_implementation project’ — corresponds to OZG catalogue meaning — ‘catalogue_PriorityDetermination’ — Conforms to OZG Catalog Meaning — ‘SH_Online ServiceExistingInventory’ — Is an online service available according to the knowledge of the department? — ‘SH_service packagenumber’ — assignment to service packages — ‘SH_service packageLong designation’ — Allocation to service packages — ‘SH_ErgaenzendeLegal Basis’ — SH supplementing the legal basis — ‘SH_application form’ — Is a paper application form available for the service? — ‘SH_DigitalisationPriorityDetermination’ — Should the performance be digitised or not? If not: Why? — ‘SH_ResponsibilityBehoerdeLevel1’ — Technically responsible department — ‘SH_ResponsibilityBehoerdeLevel2’ — Technically responsible department — ‘SH_ResponsibilityBehoerde Ebene2a’ — Professionally responsible other organisational unit — ‘SH_ResponsibilityBehoerdeLevel3’ — Technically Responsible Unit — ‘SH_SpecialistresponsibilityBehoerdeVersponsibleResponsible’ — The professional responsible is also responsible for performance? — ‘SH_Performance ResponsibilityBehoerde Ebene1’ — Responsible for performance — ‘SH_Performance ResponsibilityBehoerde Ebene2’ — Department responsible for performance — ‘SH_Performance ResponsibilityBehoerde Ebene2a’ — Other organisational unit responsible for performance — ‘SH_Performance ResponsibilityBehoerde Ebene3’ — Unit responsible for performance — ‘catalogue_OZGID’ — corresponds to OZG catalogue meaning — ‘JiraHandling Responsibility’ — When entering ‘EfA’ → The online service of another federal state is to be used. — ‘JiraStatus’ — ‘Traffic light infos’ on the status of the performance: ‘Backlog’ and *empty* = ‘ROT’/‘Finish’ = ‘GREEN’/Other entry = ‘GELF’