@php $configData = Helper::appClasses(); @endphp @extends('layouts/layoutMaster') @section('title', 'Metadata Registry') @section('content') @section('title', 'Logistics Dashboard - Apps') @section('vendor-style') @vite(['resources/assets/vendor/libs/apex-charts/apex-charts.scss', 'resources/assets/vendor/libs/datatables-bs5/datatables.bootstrap5.scss', 'resources/assets/vendor/libs/datatables-responsive-bs5/responsive.bootstrap5.scss']) @endsection @section('page-style') @vite('resources/assets/vendor/scss/pages/app-logistics-dashboard.scss') @endsection @section('vendor-script') @vite(['resources/assets/vendor/libs/apex-charts/apexcharts.js', 'resources/assets/vendor/libs/datatables-bs5/datatables-bootstrap5.js']) @endsection @section('page-script') @vite('resources/assets/js/app-logistics-dashboard.js') @endsection @section('content')
The metadata registry maintains a list of all metadata fields available in the repository. These fields may be divided amongst multiple schemas. However, DSpace requires the qualified Dublin Core schema.