museum-digital/translation-json-archive
34
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Initial

Browse Source
This commit is contained in:
Joshua Ramon Enslin 2022-10-05 15:43:28 +02:00
commit 223e2a87ca
Signed by: jrenslin
GPG Key ID: 46016F84501B70AE
94 changed files with 1648 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
LICENSE Normal file
View File

@ -0,0 +1,21 @@
MIT License
Copyright (c) 2020-2021 museum-digital
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

3
README.md Normal file
View File

@ -0,0 +1,3 @@
# Archive for translation files
... of museum-digital projects, that no longer use the md translation tool.

110
md-cms/de/mdcms-backend.json Normal file
View File

@ -0,0 +1,110 @@
{
"translations": {
"submit": "Abschicken",
"options": "Optionen",
"start": "Start",
"fileUpload": "Dateiupload",
"users": "Benutzer",
"pages": "Seiten",
"pagesOverview": "Seiten\u00fcbersicht",
"newPage": "Eine neue Seite hinzuf\u00fcgen",
"edit": "Bearbeiten",
"settings": "Einstellungen",
"administration": "Administration",
"tools": "Tools",
"preview": "Vorschau",
"banner": "Banner",
"delete": "L\u00f6schen",
"general": "Generelle Einstellungen",
"security": "Sicherheit",
"aboutThisSite": "\u00dcber diese Seite",
"numberOfPages": "Anzahl aller Seiten",
"numberOfPublicPages": "Anzahl aller \u00f6ffentlichen Seiten",
"phpVersion": "PHP-Version",
"aboutMDCMS": "\u00dcber md:cms",
"aboutMDCMS_content": "<p>md:cms ist ein Content Management System f\u00fcr museumsbezogene Websites. Es bietet verschiedene Funkionen zum Einbetten von Inhalten aus einer gegebenen Instanz von museum-digital. Zur Benutzung von md:cms sind ein Webserver mit PHP7 und ein SSL-Zertifikat f\u00fcr ihre Domain die einzigen Vorraussetzungen.<\/p>",
"integrationWithMD": "Integration mit museum-digital",
"languageUnavailable": "Diese Sprache ist nicht verf\u00fcgbar",
"settingsUpdated": "Einstellungen wurden gespeichert",
"storedEditsToPage": "Bearbeitungen an dieser Seite wurden gespeichert",
"storedEditsToPageElement": "Bearbeitungen an diesem Element wurden gespeichert",
"deletedPage": "Seite wurde gel\u00f6scht",
"staticPageTitle": "Seitentitel",
"staticPageContent": "Seiteninhalt",
"staticPagePublic": "Entwurf \/ \u00d6ffentlich",
"helpStaticPagePublic": "<p>Mithilfe dieses Schalters k\u00f6nnen Sie das Dokument ver\u00f6ffentlichen.<\/p>",
"staticPageHigher": "H\u00f6here Seite in Hierarchie",
"helpStaticPageHigher": "<p>Die n\u00e4chst-h\u00f6here Seite in der Seitenhierarchie.<\/p>",
"helpPagesOverview": "<p>Diese Seite bietet eine \u00dcbersicht aller statischen Seiten.<\/p>",
"helpSettings": "<p>Auf dieser Seite k\u00f6nnen Sie die generellen Einstellungen der Seite bearbeiten.<\/p>",
"helpURL": "<p>URL der Seite.<\/p>",
"startPage": "Startseite",
"helpStartPage": "<p>Die Startseite des \u00f6ffentlichen Bereichs.<\/p>",
"mdImgFolder": "Medienortner (md)",
"helpMDimgFolder": "<p>Der Ordner, in dem bei der verlinkten Instanz von museum-digital Mediendateien gespeichert werden.<\/p>",
"logo": "Logo",
"helpLogo": "<p>Das Logo dieser Seite. Der Inhalt dieses Feldes wird haupts\u00e4chlich f\u00fcr das kleine Icon, das Sie oben neben dem Titel in ihrem Browser sehen, verwendet.<\/p>",
"mdVersion": "Version \/ Instanz von museum-digital",
"helpMDVersion": "<p>Viele Inhalte k\u00f6nnen durch eine Verkn\u00fcpfung mit museum-digital eingebunden werden. Daf\u00fcr muss jedoch spezifiziert werden, welche Instanz von museum-digital verkn\u00fcpft sein soll. Tragen Sie etwa <code>https:\/\/rlp.museum-digital.de\/<\/code> ein.<\/p>",
"settingsPageTitle": "Titel der Webseite",
"helpSettingsPageTitle": "<p>Der Titel, der in ihrem Browser gezeigt wird. K\u00f6nnte etwa der Name des Museums sein.<\/p>",
"admin": "Admin",
"helpAdmin": "<p>Ist der Benutzer ein Administrator?<\/p>",
"language": "Sprache",
"helpLanguage": "<p>Die hier genutzte Sprache.<\/p>",
"sendHTTPHeaders": "Zus\u00e4tzliche HTTP-Header senden",
"helpSendHTTPHeaders": "<p>md:cms kann zus\u00e4tzliche HTTP-Header senden, um die Sicherheit ihrer Benutzer zu erh\u00f6hen.<\/p>\r\n<p>Auch Ihr Server-Administrator kann diese Header auf Server-Ebene senden. Diese Option ist wesentlich besser, als dass md:cms diese Aufgabe \u00fcbernimmt, wird aber nach wie vor h\u00e4ufig nicht umgesetzt. Sollte der Serveradministrator schon daf\u00fcr gesorgt haben, dass die Header gesendet werden, deaktivieren Sie bitte diese Option. F\u00fcr weitere Informationen ist das <a href='https:\/\/observatory.mozilla.org\/'>Mozilla Observatory<\/a> eine hilfreiche Resource.<\/p>\r\n <p>\r\n The default headers sent are the following:\r\n <pre><code>\r\n X-Content-Type-Options: nosniff\r\n X-XSS-Protection: 1; mode=block\r\n Strict-Transport-Security: max-age=31536000; preload\r\n Referrer-Policy: strict-origin\r\n <\/code><\/pre>\r\n <\/p>",
"CSPimageSources": "Bildquellen (Whitelist)",
"helpCSPimageSources": " <p>Um die Sicherheit Ihrer Benutzer zu erh\u00f6hen, wei\u00dft md:cms den Browser der Benutzer an, Bilder nur von bekannten Quellen zu laden. Standardm\u00e4\u00dfig sind diese nur die derzeit genutzte Domain und die verkn\u00fcpfte Version von museum-digital.<\/p>\r\n <p>M\u00f6chten Sie etwa Bilder von flickr.com einbinden, so k\u00f6nnen Sie diese entweder herunterladen und hier wieder heraufladen, oder sie whitelisten flickr. Um Domains zu whitelisten, tragen Sie sie bitte - durch ein Komma getrennt - in das Eingabefeld ein. Z.B.:<br \/>\r\n <code>https:\/\/www.flickr.com https:\/\/www.google.com<\/code>\r\n <\/p>",
"CSPobjectSources": "Objektquellen (Whitelist)",
"helpCSPobjectSources": " <p>Um die Sicherheit Ihrer Benutzer zu erh\u00f6hen, wei\u00dft md:cms den Browser der Benutzer an, Objekte und Frame-Inhalte nur von bekannten Quellen zu laden. Standardm\u00e4\u00dfig sind diese nur die derzeit genutzte Domain und die verkn\u00fcpfte Version von museum-digital.<\/p>\r\n <p>M\u00f6chten Sie etwa Videos von youtube.com einbinden, so k\u00f6nnen Sie youtube hier whitelisten. Um Domains zu whitelisten, tragen Sie sie bitte - durch ein Komma getrennt - in das Eingabefeld ein. Z.B.:<br \/>\r\n <code>https:\/\/www.youtube.com https:\/\/www.vimeo.com<\/code>\r\n <\/p>",
"maxFileSize": "Maximale Upload-Gr\u00f6\u00dfe",
"helpMaxFileSize": "<p>Die maximale Dateigr\u00f6\u00dfe von Uploads.<\/p>",
"cacheRefreshInterval": "Interval der Zwischenspeicherung",
"helpCacheRefreshInterval": "<p>Mit dieser Einstellung bestimmen Sie, wie h\u00e4ufig Inhalte von museum-digital neu geladen werden. Die Frequenz wird in Sekunden bemessen.\r\n <ul>\r\n <li>Bei einem Wert von <code>0<\/code> ist der Zwischenspeicher abgeschaltet<\/li>\r\n <li>Mit einem niedriegen Wert erhalten sie ggfs. aktuellere Daten, aber die Seite l\u00e4dt langsamer.<\/li>\r\n <li>Mit einem hohen Wert k\u00f6nnen ihre Inhalte leicht veraltet sein, aber die Seite l\u00e4dt wesentlich schneller.<\/li>\r\n <\/ul>\r\n <\/p>",
"settingsUsedCSS": "Theme",
"helpSettingsUsedCSS": "<p>Hier k\u00f6nnen Sie das zu benutzende Theme ausw\u00e4hlen. Neue Themes k\u00f6nnen per FTP installiert werden.<\/p>",
"hideInstitution": "Institution verstecken",
"helpHideInstitution": "<p>Wird diese Seite nur von einem einzelnen Museum genutzt, ist die Anzeige zu welchem Museum ein Objekt, eine Sammlung, etc. geh\u00f6rt obsolet. Mit diesem Schalter k\u00f6nnen Sie den entsprechenden Text verstecken.<\/p>",
"limitToInstitutions": "Beschr\u00e4nkung auf Institution(en)",
"helpLimitToInstitutions": "<p>md:cms bietet die M\u00f6glichkeit, die angezeigten und von museum-digital eingebundenen Objekte, Sammlungen, etc. auf solche zu beschr\u00e4nken, die zu ausgew\u00e4hlten Institutionen geh\u00f6ren. Wird diese Seite etwa von einem Museum genutzt, so sollten die Inhalte anderer Museen m\u00f6glicherweise nicht hier erscheinen. Um diese Beschr\u00e4nkung zu aktivieren, tragen Sie einfach die Museums-IDs der erlaubten Institutionen bei museum-digital in das nebenstehende Feld ein - getrennt durch ein Komma, falls es mehrere sind.<\/p>",
"IDatMD": "ID bei museum-digital",
"embedFromMD": "Einbetten aus museum-digital",
"helpEmbedFromMD": "<p>In diesem Feld k\u00f6nnen Sie sich einen Platzhalter generieren, mit dem Sie Inhalte aus museum-digital einbinden k\u00f6nnen. Daf\u00fcr m\u00fcssen Sie zuerst den Typ der Einbettung ausw\u00e4hlen, dann die zus\u00e4tzlichen URL-Parameter eingeben (bei Objekten w\u00e4re das etwa: Kachel-Modus ausw\u00e4hlen, dann unten \"oges=1005\" eingeben). Danach k\u00f6nnen Sie den Platzhalter mit einem klick auf \"Generieren\" generieren. Anschlie\u00dfend k\u00f6nnen Sie ihn durch copy-paste im Text verwenden.<\/p>",
"footer": "Fu\u00dfzeile",
"helpfooter": "<p>Auf dieser Seite k\u00f6nnen Sie die Fu\u00dfzeile bearbeiten. Um keine Fu\u00dfzeile anzuzeigen, stellen Sie bitte sicher, dass das Eingabefeld <i>keinen<\/i> Inhalt hat.<\/p>",
"helpbanner": "<p>Auf dieser Seite k\u00f6nnen Sie das Banner bearbeiten. Um kein Banner anzuzeigen, stellen Sie bitte sicher, dass das Eingabefeld <i>keinen<\/i> Inhalt hat.<\/p>",
"aside": "Seitenspalte",
"helpaside": "<p>Auf dieser Seite k\u00f6nnen Sie die Seitenspalte bearbeiten. Um keine Seitenspalte anzuzeigen, stellen Sie bitte sicher, dass das Eingabefeld <i>keinen<\/i> Inhalt hat.<\/p>",
"welcomeMsg": "Willkommensnachricht",
"helpwelcomeMsg": "<p>Auf dieser Seite k\u00f6nnen Sie die Willkommensnachricht bearbeiten, die nach dem Einloggen auf der Startseite des Eingabebereichs erscheint.<\/p>",
"urlAbbr": "<abbr title=\"Uniform Resource Locator\">URL<\/abbr>",
"url": "URL",
"specifyToEdit": "Bitte spezifizieren Sie, was Sie bearbeiten wollen.",
"specifyToDelete": "Bitte spezifizieren Sie, was Sie l\u00f6schen m\u00f6chten.",
"usersOverview": "\u00dcbersicht aller Benutzer",
"listUsers": "Benutzer auflisten",
"addUser": "Benutzer hinzuf\u00fcgen",
"userAdded": "Neuer Benutzer wurde erfolgreich angelegt: ",
"username": "Benutzername",
"helpUsername": "<p>Der Benutzername des Benutzers. Der Benutzer loggt sich mit dem Benutzernamen ein.<\/p><p><b>Obligatorisch.<\/b><\/p>",
"email": "Email-Adresse",
"helpEmail": "<p>Email-Adresse des Benutzers. Dies wird vorrausgesetzt, um den Benutzer sp\u00e4ter kontaktieren zu k\u00f6nnen.<\/p><p><b>Obligatorisch.<\/b><\/p>",
"password": "Passwort",
"passwordVerify": "Passwort (Verifikation)",
"helpPassword": "<p>Passwort des Benutzers. Das Passwort muss mindestens acht (8) Zeichen lang sein.<\/p><p><b>Obligatorisch.<\/b><\/p>",
"realName": "Realname",
"helpRealName": "<p>Der volle Realname des Benutzers.<\/p><p><b>Obligatorisch.<\/b><\/p>",
"helpUsers": "<p>Auf dieser Seite k\u00f6nnen Sie eine \u00dcbersicht aller Benutzer sehen. Des weiteren k\u00f6nnen Sie hier neue Benutzer hinzuf\u00fcgen.<\/p>",
"helpStart": "<p>Dies ist die Startseite von md:cms.<\/p>",
"helpSinglePage": "<p>Auf dieser Seite k\u00f6nnen Sie statische Seiten hinzuf\u00fcgen und bearbeiten.<\/p>",
"requiredValueMissing": "Ein obligatorischer Wert fehlt.",
"passwordsDoNotMatch": "Die Passw\u00f6rter stimmen nicht \u00fcberein.",
"passwordTooShort": "Das eingegebene Passwort ist zu kurz.",
"deletedFile": "Datei wurde gel\u00f6scht",
"uploadedFile": "Datei wurde heraufgeladen",
"fileUploadError": "Ein Fehler ist aufgetreten",
"filetypeNotWhitelisted": "Dateityp ist nicht erlaubt",
"fileTooLarge": "Die Datei ist zu gro\u00df"
}
}

110
md-cms/en/mdcms-backend.json Normal file
View File

@ -0,0 +1,110 @@
{
"translations": {
"submit": "Submit",
"options": "Options",
"start": "Start",
"fileUpload": "File Uploads",
"users": "Users",
"pages": "Pages",
"pagesOverview": "Overview of Pages",
"newPage": "Adding a Page",
"edit": "Edit",
"settings": "Settings",
"administration": "Administration",
"tools": "Tools",
"preview": "Preview",
"banner": "Banner",
"delete": "Delete",
"general": "General Settings",
"security": "Security",
"aboutThisSite": "About this page",
"numberOfPages": "Number of pages (overall)",
"numberOfPublicPages": "Number of pages (public)",
"phpVersion": "PHP Version",
"aboutMDCMS": "About md:cms",
"aboutMDCMS_content": "<p>md:cms is a content management system for museum-related websites. It offers many functions for embedding contents from museum-digital. The only requirements are a web server running PHP7 and SSL encryption for the domain.<\/p>",
"integrationWithMD": "Integration with Museum-Digital",
"languageUnavailable": "This language is not available",
"settingsUpdated": "Updated settings",
"storedEditsToPage": "Stored edits to page",
"storedEditsToPageElement": "Stored edits to page element",
"deletedPage": "Removed page",
"staticPageTitle": "Page title",
"staticPageContent": "Page content",
"staticPagePublic": "Draft\/Public",
"helpStaticPagePublic": "<p>Using this switch, you can publish the document.<\/p>",
"staticPageHigher": "Higher page in hierarchy",
"helpStaticPageHigher": "<p>The next higher page in the hierarchy of pages.<\/p>",
"helpPagesOverview": "<p>This page provides an overview of all static pages available here.<\/p>",
"helpSettings": "<p>On this page you can edit the general settings of the page<\/p>",
"helpURL": "<p>URL of the page. Filling out this field helps with optimization for search engines.<\/p>",
"startPage": "Start page",
"helpStartPage": "<p>The start page of the public site.<\/p>",
"mdImgFolder": "Image folder (md)",
"helpMDimgFolder": "<p>The folder in which image files are stored in the given instance of museum-digital.<\/p>",
"logo": "Logo",
"helpLogo": "<p>The logo of the site. Is mainly used for the little icon you see in the browser, right next to the title of the tab.<\/p>",
"mdVersion": "Version of Museum-Digital",
"helpMDVersion": "<p>Much of the data in md:cms is pulled from museum-digital.<\/p>",
"settingsPageTitle": "Website Title",
"helpSettingsPageTitle": "<p>The page title displayed in the browser. Could be, e.g., your museum's name.<\/p>",
"admin": "Admin",
"helpAdmin": "<p>Is the user an administrator?<\/p>",
"language": "Language",
"helpLanguage": "<p>The default language of this version of md:cms.<\/p>",
"sendHTTPHeaders": "Send additional HTTP Headers",
"helpSendHTTPHeaders": "<p>md:cms can send additional directives to the browser to increase security. Your server administrator can set these server wide, and if they have done so already, you should disable this option (this is by far the prefered way). In most cases, server administrators have not opted to do so yet, and keeping this option enabled makes sense. If you want to inquire into this further, the <a href='https:\/\/observatory.mozilla.org\/'>Mozilla Observatory<\/a> is a useful resource.<\/p>\r\n <p>\r\n The default headers sent are the following:\r\n <pre><code>\r\n X-Content-Type-Options: nosniff\r\n X-XSS-Protection: 1; mode=block\r\n Strict-Transport-Security: max-age=31536000; preload\r\n Referrer-Policy: strict-origin\r\n <\/code><\/pre>\r\n <\/p>",
"CSPimageSources": "Image sources (whitelist)",
"helpCSPimageSources": " <p>To increase security, md:cms directs browsers to refrain from loading images from any but the whitelisted sources. By default, only the current domain and the linked version of museum-digital are whitelisted.<\/p>\r\n <p>If you, for example, want to embed images from flickr.com, you either need to download the images and upload them here, or you whitelist flickr. To whitelist domains, please enter them one by one into the field, separated by whitespaces. E.g.<br \/>\r\n <code>https:\/\/www.flickr.com https:\/\/www.google.com<\/code>\r\n <\/p>",
"CSPobjectSources": "Object sources (whitelist)",
"helpCSPobjectSources": " <p>To increase security, md:cms directs browsers to refrain from loading frames and objects from any but the whitelisted sources. By default, only the current domain and the linked instance of museum-digital are whitelisted.<\/p>\r\n <p>If you, for example, want to embed videos from youtube.com, you need to whitelist youtube. To whitelist domains, please enter them one by one into the field, separated by whitespaces. E.g.<br \/>\r\n <code>https:\/\/www.youtube.com https:\/\/www.vimeo.com<\/code>\r\n <\/p>",
"maxFileSize": "Maximum upload size",
"helpMaxFileSize": "<p>The maximum file size of file uploads.<\/p>",
"cacheRefreshInterval": "Cache Refresh Interval",
"helpCacheRefreshInterval": "<p>This setting determines how often content from museum-digital is refreshed(the number equals X seconds).\r\n <ul>\r\n <li>Setting it to <code>0<\/code> disables it<\/li>\r\n <li>Using a low value, means more accurate data, but slower loading time.<\/li>\r\n <li>Using a high value, means data could be slightly outdated, but makes loading much faster.<\/li>\r\n <\/ul>\r\n <\/p>",
"settingsUsedCSS": "Theme",
"helpSettingsUsedCSS": "<p>Select the used theme. New themes can be installed using FTP.<\/p>",
"hideInstitution": "Hide institution",
"helpHideInstitution": "<p>If this page is used for only a single museum, you can opt to not display the institution on tiles for exhibitions, collections, etc. by moving the slider to the right.<\/p>",
"limitToInstitutions": "Limit to institutions",
"helpLimitToInstitutions": "<p>The CMS offers the option to display objects, exhibitions, etc. from museum-digital based on their ID. By default all objects can be accessed using this functionality. To not display data that is not yours, you can restrict the data by the linked institution.<\/p>\r\n <p>Enter IDs of institutions separated by commas.<\/p>",
"IDatMD": "ID at museum-digital",
"embedFromMD": "Embed from museum-digital",
"helpEmbedFromMD": "<p>In this area, you can generate placeholder, with which you can embed contents from museum-digital. To do so, you first need to select an embedding type, then you can enter additional parameters determining what you want to embed. If you want to - for example - embed the object with ID 1005 as a tile, select the object tile embedding type. Then enter oges=1005 into the field appearing below (these parameters can be seen in the URL when surfing museum-digital). Once you're done with that, you can generate the placeholder by clicking on \"Generate\". Finally, the placeholder appears, ready to be copy-pasted and used in the text.<\/p>",
"footer": "Footer",
"helpfooter": "<p>On this page, you can edit the footer. To not display a footer, simply empty this page.<\/p>",
"helpbanner": "<p>On this page, you can edit the banner.<\/p>",
"aside": "Sidebar",
"helpaside": "<p>On this page, you can edit the sidebar. To not display a sidebar at all, simply empty this page.<\/p>",
"welcomeMsg": "Welcome Message",
"helpwelcomeMsg": "<p>On this page, you can edit the welcome message appearing on the start page of the input interface (what people see when they log in).<\/p>",
"urlAbbr": "<abbr title=\"Uniform Resource Locator\">URL<\/abbr>",
"url": "URL",
"specifyToEdit": "Please specify what you want to edit",
"specifyToDelete": "Please specify what you want to delete",
"usersOverview": "Overview of All Users",
"listUsers": "List users",
"addUser": "Add user",
"userAdded": "Successfully added new user:",
"username": "Username",
"helpUsername": "<p>Username of the user. The user logs in with his or her username.<\/p><p><b>Required.<\/b><\/p>",
"email": "Email Address",
"helpEmail": "<p>Email address of the user. This needs to be saved, to be able to contact the user later on.<\/p><p><b>Required.<\/b><\/p>",
"password": "Password",
"passwordVerify": "Password (Verification)",
"helpPassword": "<p>Password of the user. The password needs to be at least 8 characters long.<\/p><p><b>Required.<\/b><\/p>",
"realName": "Real name",
"helpRealName": "<p>Full, real name of the user. The full name is displayed next to entries by that person.<\/p><p><b>Required.<\/b><\/p>",
"helpUsers": "<p>On this page, you can access an overview of all users. You can also add new users here.<\/p>",
"helpStart": "<p>This is the start page of md:cms.<\/p>",
"helpSinglePage": "<p>On this page, you can add or edit static pages.<\/p>",
"requiredValueMissing": "A required value is missing",
"passwordsDoNotMatch": "The passwords do not match",
"passwordTooShort": "The password is too short",
"deletedFile": "Deleted file",
"uploadedFile": "Uploaded file",
"fileUploadError": "Error uploading file",
"filetypeNotWhitelisted": "Filetype is not in whitelist",
"fileTooLarge": "The file is too large"
}
}

14
mdorg/de/about.json Normal file
View File

@ -0,0 +1,14 @@
{
"tlAbout": {
"pageTitle": "\u00dcber museum-digital :: museum-digital",
"pageDescription": "Wer oder was ist museum-digital? Wir sind ein Projekt mit dem Ziel, die Digitalisierung in Museen und von Museumsdaten weiterzubringen.",
"pageKeywords": "Museen, Digitalisierung, Community, Forschung",
"about_title": "\u00dcber museum-digital",
"about_introduction": "museum-digital ist eine Inititive von Museen. Die Initiative besteht seit 2009. Sie entstand aus dem Versuch einen m\u00f6glichst einfachen Weg zu entwickeln, um Informationen \u00fcber Museen und die von ihnen verwahrten Objekte online zu stellen. Aus den urspr\u00fcnglich 6 beteiligten Museen sind mittlerweile mehr als 600 geworden und l\u00e4ngst haben sich auch die Ziele erweitert. Die einfache Publikation in einer Datenbank wurde durch weitere Pr\u00e4sentationsformen erweitert, vor allem aber ist gutes Inventarisieren ebenfalls zu einem zentralen Ziel geworden. Bei museum-digital entwickeln wir gemeinsam Software mit dem Ziel, die Inventarisierung und die Online-Stellung nicht nur einfach, sondern jede qualit\u00e4tvolle Erfassung zu einer Freude zu machen. \r\n",
"about_resources": "Resourcen",
"logos_caption": "Hier k\u00f6nnen Sie die verschiedenen von museum-digital verwendeten Logos zum Download finden.",
"background_title": "Wo kommen wir her - und wo geht es hin?",
"background_content": "Als sich im Februar 2009 im Kreismuseum Bitterfeld mehrere Museen des Museumsverbandes Sachsen-Anhalt trafen, um die Arbeitsgemeinschaft Digitalisierung des Museumsverbandes Sachsen-Anhalt zu gr\u00fcnden legten sie den Grundstein f\u00fcr museum-digital. Damals wurden gemeinsame Grunds\u00e4tze aufgestellt, das gemeinsame Ziel definiert und eine Machbarkeitsstudie durchgef\u00fchrt. Schon an dieser Studie beteiligten sich Museen aus dem Museumsverband Rheinland-Pfalz. Best\u00e4ndig wuchs die Zahl von Museen und Verb\u00e4nden, die an museum-digital mitwirken. Aus dieser Verwurzelung in der Region entstand die aktuelle Struktur von museum-digital, das in verschiedenen Instanzen organisiert ist, die im Prinzip voneinander unabh\u00e4ngig sind. Dennoch gibt es f\u00fcr jede Sprache einen Pool von kontrollierten Begriffen, den alle Instanzen dieses Sprachgebiets gemeinsam nutzen. Dieser Pool wird gemeinsam gepflegt. Objektdatenbank(en) und Normdatenpool sind die Grundlage f\u00fcr gemeinsames Publizieren und qualit\u00e4tvolles Inventarisieren.\r\n",
"the_future": "museum-digital ist auf Mehrsprachigkeit ausgerichtet und stets offen f\u00fcr neue Mitstreiter. Entwicklung geschieht nach Bedarf. Woimmer sich mehrere Museen zusammentun k\u00f6nnen sie museum-digital nutzen. Bei Bedarf wird eine weitere Instanz eingef\u00fchrt oder es werden andere Kooperationswege geschaffen. Weil der Bedarf die Weiterentwicklung bestimmt folgt museum-digital keinem festgef\u00fcgten Plan."
}
}

10
mdorg/de/about_faq.json Normal file
View File

@ -0,0 +1,10 @@
{
"tlFaq": {
"how_to_join_question": "Wie kann ein Museum bei museum-digital mitmachen?",
"how_to_join_answer": "To join museum-digital, contact the admin of your local instance of museum-digital. If there is no regional instance for where you are yet, please contact us using the contact page.",
"pageTitle": "Frequently Asked Questions",
"pageDescription": "H\u00e4ufig gestellte Fragen zu museum-digital.",
"pageKeywords": "FAQ, Frequently Asked Questions, museums, collections, inventorization",
"faq_title": "Frequently Asked Questions"
}
}

11
mdorg/de/about_presentations.json Normal file
View File

@ -0,0 +1,11 @@
{
"tlPresentations": {
"pageTitle": "Pr\u00e4sentationen :: museum-digital",
"pageDescription": "Eine Liste von Pr\u00e4sentationen \u00fcber museum-digital, mal mit Folien, mal mit Video.",
"pageKeywords": "museum-digital, Pr\u00e4sentationen, Foliensatz, Vortrag",
"presentations_title": "Pr\u00e4sentationen \u00fcber museum-digital",
"presentations_introduction": "\u00dcber die Jahre wurden viele Vortr\u00e4ge \u00fcber die Arbeit von und an museum-digital gehalten. Hier k\u00f6nnen Sie eine Auswahl dieser Vortr\u00e4ge - so vorhanden mit Link zu Videos und Foliens\u00e4tzen - finden.",
"date": "Datum",
"open": "\u00d6ffnen"
}
}

11
mdorg/de/about_publications.json Normal file
View File

@ -0,0 +1,11 @@
{
"tlPublications": {
"pageTitle": "Ver\u00f6ffentlichungen :: museum-digital",
"pageDescription": "Auf dieser Seite findet sich eine Liste aller Publication zu und \u00fcber museum-digital.",
"pageKeywords": "museum-digital, Forschung, Ver\u00f6ffentlichungen, Wissenschaft",
"publications_title": "Ver\u00f6ffentlichungen \u00fcber museum-digital",
"publications_introduction": "Die Flexibilit\u00e4t und Nicht-Kommerzialit\u00e4t von museum-digital bieten Raum f\u00fcr Innovation und Forschung. \u00dcber die Jahre sind eine Reihe von Texten \u00fcber oder auf Basis von museum-digital ver\u00f6ffentlicht worden. Im folgenden findet sich eine Liste dieser Ver\u00f6ffentlichungen.\t",
"Rohde-Enslin2015": "PuQi - Ein Cleverer Weg bessere Daten zu produzieren",
"Kopp-Sievers2015": ""
}
}

11
mdorg/de/calendar.json Normal file
View File

@ -0,0 +1,11 @@
{
"tlCalendar": {
"dateformat": "d.m.Y H:i",
"calendarPageTitle": "Kalender:: museum-digital",
"calendarPageDescription": "Auf dieser Seite k\u00f6nnen Sie aktuelle Veranstaltungen rund um museum-digital finden, z.B. Schulungen.",
"calendarPageKeywords": "museum-digital, Kalender, Veranstaltungen, Seminare",
"calendar_title": "Kalender",
"calendar_introduction": "Auf dieser Seite k\u00f6nnen Sie aktuelle Veranstaltungen rund um museum-digital finden, z.B. Schulungen.",
"attendees": "Teilnehmende"
}
}

11
mdorg/de/contact.json Normal file
View File

@ -0,0 +1,11 @@
{
"tlContact": {
"pageTitle": "Kontakt :: museum-digital",
"pageDescription": "Mit museum-digital in Kontakt treten.",
"pageKeywords": "Kontaktseite, museum-digital",
"contacts_title": "Kontakt",
"contacts_introduction": "\"museum-digital\" ist eine gemeinsame Unternehmung von Museen und Museumsverb\u00e4nden. Sie k\u00f6nnen uns hier kontaktieren:",
"e-mail": "e-Mail",
"impressum": "Impressum"
}
}

37
mdorg/de/dashboard.json Normal file
View File

@ -0,0 +1,37 @@
{
"tlDashboard": {
"pageTitle": "Dashboard :: museum-digital",
"pageDescription": "Facts, Figures, Benchmarks zu museum-digital und seinen verschiedenen Instanzen",
"pageKeywords": "museum-digital, Statistik, Graphen, Museen, Digitalisierung",
"dashboard": "Dashboard",
"dashboard_introduction": "Zahlen und Schaubilder zur Entwicklung von museum-digital",
"in_the_database": "Eintr\u00e4ge in der Datenbank",
"objects": "Objekte",
"museums": "Museen",
"collections": "Sammlungen",
"literature_entries": "Literatureintr\u00e4ge",
"exhibitions": "Ausstellungen",
"appointments": "Veranstaltungen",
"user_accounts": "User-Accounts",
"images": "Abbildungen",
"visitor_stats": "Besucherstatistik",
"visitors_yesterday": "Besucher (gestern)",
"visitors_this_month": "Besucher in diesem Monat",
"controlled_vocabularies": "Kontrollierte Vokabulare",
"popular_entries_in_german": "Beliebte deutschsprachige Eintr\u00e4ge",
"title_actors": "Akteure",
"title_places": "Orte",
"title_tags": "Schlagworte",
"popular_entries_in_hungarian": "Beliebte ungarisch-sprachige Eintr\u00e4ge",
"controlled_vocabularies_figcaption_german": "Kontrollierte Vokabulare in der deutschsprachigen Datenbank<br\/>Von Links: Personen, Orte, Zeiten, Tags",
"controlled_vocabularies_figcaption_hungarian": "Kontrollierte Vokabulare in der ungarisch-sprachigen Datenbank<br\/>Von Links: Personen, Orte, Zeiten, Tags",
"was_founded": "museum-digital wurde am %s gegr\u00fcndet",
"is_days_old": "museum-digital ist %s Tage alt",
"avg_obj_desc_length": "Eine durchschnittliche Objektbeschreibung ist %s Zeichen lang",
"avg_puqi_value": "Der durchschnittliche <a href=\"https:\/\/journals.uic.edu\/ojs\/index.php\/UC\/article\/download\/6218\/5067\">PuQi<\/a>-Wert aller \u00f6ffentlichen Objekte betr\u00e4gt",
"development": "Entwicklung",
"git_commits_by_project_and_month": "Entwicklungsinteraktionen nach Projekt und Monat",
"quality": "Qualit\u00e4t",
"popular_entries": "Beliebte Eintr\u00e4ge"
}
}

8
mdorg/de/errorPages.json Normal file
View File

@ -0,0 +1,8 @@
{
"tlErrors": {
"403_title": "Verboten",
"403_text": "Sie d\u00fcrfen diese Seite nicht sehen. Bitte benutzen Sie die obige Navigation, um sichtbare Seiten zu erreichen.",
"404_title": "Autsch ... Hier ist nichts zu sehen ...",
"404_text": "Hier ist nichts zu finden. Mithilfe der oberen Navigation k\u00f6nnen Sie die Inhalte der Seite durchbl\u00e4ttern."
}
}

10
mdorg/de/footer.json Normal file
View File

@ -0,0 +1,10 @@
{
"tlFooter": {
"contact": "Kontakt",
"impressum": "Impressum",
"privacy": "Datenschutzerkl\u00e4rung",
"search": "Suche",
"search_in_mdorg": "museum-digital.org durchsuchen",
"search_in_md": "Nach Objekten suchen"
}
}

14
mdorg/de/home.json Normal file
View File

@ -0,0 +1,14 @@
{
"tlHome": {
"pageTitle": "museum-digital",
"pageDescription": "museum-digital ist eine Initiative zur Digitalisierung von Museen",
"pageKeywords": "Museen, Digitalisierung, Community, Forschung",
"opener_title": "Museen zeigen sich der Welt - so wie sie es wollen",
"opener_text": "museum-digital ist eine Initiative, ist eine Software-Suite und ist eine Platform. Im Januar 2009 kamen im Bitterfelder Kreismuseum Mitarbeiter und Mitarbeiterinnen von Museen aus Sachsen-Anhalt zusammen und beschlossen den Weg ins Netz zu wagen. Das war die Geburtsstunde von museum-digital. Schon damals war klar: Erfolgreich im Netz sichtbar werden, das kann nur gemeinsam gelingen. Gemeinsam wird die Software entwickelt und gemeinsam pr\u00e4sentieren sich die Museen im Netz. Was damals als kleine Gemeinschaft begann ist zu einer Community gewachsen, die Sprach- und L\u00e4ndergrenzen \u00fcberwindet.",
"community_title": "Gemeinsam gut",
"community_text": "Jedes Museum hat eigene M\u00f6glichkeiten und eigene Ziele. Bei museum-digital arbeiten alle zusammen. Anders als aktuelle Portale im Internet bietet museum-digital sowohl M\u00f6glichkeiten zur <a href=\"\/software\/frontend\">Publikation<\/a> als auch zur <a href=\"\/software\/musdb\">Erfassung und Inventarisierung<\/a> von Museumsobjekt-Informationen. F\u00fcr jede Sprachversion gibt es einen gemeinsam genutzten und gepflegten Pool von kontrollierten und angereicherten Begriffen. Dieser zentralen Pool spart viel Arbeit, hilft Verkn\u00fcpfungen sichtbar zu machen und ist die Grundlage des erfolgreichen Ver\u00f6ffentlichens im Netz.\r\n<\/p>\r\n<p>\r\n<!-- Die Bereitstellung entsprechender Kommunikationskan\u00e4le bei museum-digital f\u00f6rdert den direkten Kontakt unter KollegeInnen \u00fcber Museumsgrenzen hinweg. -->\r\nDie Community von museum-digital schlie\u00dft niemanden aus, jedes Museum kann sich beteiligen - die gr\u00f6\u00dften Sch\u00e4tze sind oft an den entlegendsten Orten zu finden.\r\nOffen sein f\u00fcr Museen aller Art und aller Gr\u00f6\u00dfen - das gelingt nur, weil Flexibilit\u00e4t und Einfachheit als oberste Zielvorgaben die Arbeit von museum-digital bestimmen. Zu den wichtigsten Grunds\u00e4tzen geh\u00f6rt dar\u00fcberhinaus, dass jedes Museum jederzeit die volle Kontrolle \u00fcber die Informationen zu seinen eigenen Objekten beh\u00e4lt.",
"counter_text_museums": "Vom Ausgangspunkt in Sachsen-Anhalt aus wuchs die Zahl der an museum-digital beteiligten Museen zun\u00e4chst in Deutschland, dann vor allem in Ungarn und dann dar\u00fcber hinaus. Museum-digital versucht m\u00f6glichst viele Sprachgrenzen auch ohne hohe Kosten f\u00fcr \u00dcbersetzer zu \u00fcberwinden und eine internationale Community entstehen zu lassen.",
"counter_text_collections": "Egal in welcher Region der Erde: Museen fassen Objekte zu Sammlungen zusammen. Die Sammlungen sind dabei oft nach gleichen Gesichtspunkten gegliedert, ein ungarisches Museum kann ebenso eine historische Glasbildsammlung haben wie ein deutsches Museum. F\u00fcr Forscher und andere Interessierte f\u00fchrt museum-digital an dieser Stelle Sammlungen mit gleichem Schwerpunkt zusammen.",
"counter_text_objects": "Alle Grenzen, ob politische, wirtschaftliche oder Sprachgrenzen haben sich im Laufe der Zeit verschoben, Kunst- und Kulturschaffende sind ein- und ausgewandert. Lange bevor die global vernetzte \u00d6konomie f\u00fcr eine internationale Verteilung von Gebrauchs- und Kunstgegenst\u00e4nden sorgte gab es einen regen Austausch und Handel. Im Ergebnis finden sich Objekte zur Geschichte einer Region in Museen ganz anderer Regionen. Museum-digital versucht einen zentralen Zugang zu solchen Objekten zu schaffen."
}
}

7
mdorg/de/impressum.json Normal file
View File

@ -0,0 +1,7 @@
{
"tlImpressum": {
"pageTitle": "Impressum",
"pageDescription": "Impressum of museum-digital.org",
"pageKeywords": "Impressum, museum-digital, museum-digital.org"
}
}

1
mdorg/de/join_us.json Normal file
View File

@ -0,0 +1 @@
[]

9
mdorg/de/mission.json Normal file
View File

@ -0,0 +1,9 @@
{
"tlMission": {
"pageTitle": "Mission und Vision :: museum-digital",
"pageDescription": "museum-digital ist ein Projekt zur Digitalisierung von Museen. Hier erl\u00e4utern wir unsere Mission",
"pageKeywords": "museum-digital, Museen, Digitalisierung, mission statement, Ziele",
"missions_title": "Mission",
"missions_introduction": "Museen und ihre Objekte geh\u00f6ren ins Netz! museum-digital hat es sich zur Aufgabe gemacht hierf\u00fcr eine einfach zu nutzende M\u00f6glicheit zu schaffen. Museen, die hausintern ihre Objekte mit einer anderen Software verwalten, steht museum-digital als Werkzeug der effektiven Web-Publikation zur Verf\u00fcgung. Allen anderen Museen, die etwa erst noch eine Software zur Objektverwaltung ben\u00f6tigen - oder mit einer bisher verwendeten Software unzufrieden sind, bietet museum-digital die entsprechenden Inventarisierungsm\u00f6glichkeiten.<\/p><p>\r\n\r\nmuseum-digital versteht sich als Community, d.h. alle Museen, die daran teilhaben k\u00f6nnen mitbestimmen welchen Aufgaben sich die Initiative stellt und in welche Richtung die Software weiterentwickelt wird. Nach und nach werden Kan\u00e4le ausgebaut und geschaffen, die den Austausch \u00fcber alle Aspekte des Digitalen im Museum unter Kollegen und KollegInnen erm\u00f6glichen.<\/p><p>\r\n\r\nmuseum-digital baut auf bestende Strukturen auf, deshalb sind es in Deutschland die Museumsverb\u00e4nde und -beratungsstellen der L\u00e4nder, die sich aktiv beteiligen und wesentliche St\u00fctzen der Initiative sind."
}
}

32
mdorg/de/navigation.json Normal file
View File

@ -0,0 +1,32 @@
{
"tlNavigation": {
"logo_alt_attribute": "Logo von museum-digital",
"news": "Neuigkeiten",
"about": "\u00dcber uns",
"resources": "Resourcen",
"software": "Software",
"software_md_ausgabe": "Ausgabe \/ Portal",
"software_musdb": "musdb",
"software_themator": "Themator",
"software_term_nodac": "md:term & nodac",
"portals": "Portale",
"terminology_work": "Terminologie-Arbeit",
"dashboard": "Dashboard",
"participate": "Mitmachen",
"mission": "Grunds\u00e4tze",
"resources_links": "Links",
"resources_documents": "Dokumente",
"third_party": "Drittanwendungen",
"publications": "Ver\u00f6ffentlichungen",
"api_based": "Third Party Tools",
"impressum": "Impressum",
"contact": "Kontakt",
"privacy": "Datenschutzerkl\u00e4rung",
"people": "Team",
"calendar": "Kalender",
"development_log": "Development Log",
"faq": "Frequently Asked Questions",
"presentations": "Pr\u00e4sentationen",
"document_archive": "Dokumentenarchiv"
}
}

16
mdorg/de/participate.json Normal file
View File

@ -0,0 +1,16 @@
{
"tlParticipate": {
"pageTitle": "Bei museum-digital mitmachen! :: museum-digital",
"pageDescription": "museum-digital ist ein Community-Project. Nat\u00fcrlich freuen wir uns \u00fcber Unterst\u00fctzung!",
"pageKeywords": "Partizipation, Mitmachen, Community",
"participate_title": "Ein Teil von museum-digital werden",
"participate_introduction": "Es gibt viele Wege bei museum-digital mitzumachen - der Kreativit\u00e4t sind da kaum Grenzen gesetzt. Direkt mitwirken bei museum-digital k\u00f6nnen vor allem Museen - doch: Die Museen zu unterst\u00fctzten qualit\u00e4tvoll zu inventarisieren und zu publizieren, etwa durch hilfreiche Kommentare, das kann jeder.",
"individuals": "Sie k\u00f6nnen einem einzelnen Museum ",
"individuals_title": "... als Einzelner oder als Gruppe",
"individuals_text": "Sie k\u00f6nnen einem einzelnen Museum durch Rat und Tat zur Seite stehen. Unter fast allen Objekten finden Sie einen Vermerk \"Ist Ihnen etwas aufgefallen ...\". Wenn Sie auf diese Zeile klicken, dann k\u00f6nnen Sie direkt zu dem jeweiligen Objekt mit dem betreffenden Museum per e-Mail in Verbindung treten. Sie k\u00f6nnen aber auch direkt zu einem der beteiligten Museen gehen und beispielsweise anbieten Objekte aus einem Bereich, in dem Sie sich besonders gut auskennen, zu bearbeiten. Eine andere M\u00f6glichkeit besteht darin dem Museum anzubieten, Qualit\u00e4tvolle Objektfotografien oder Scans der Bildersammlung zu erstellen.",
"local_museum_title": "Helping Out at Your Local Museum",
"local_museum_text": "Many, if not most, museums welcome little more than a helping hand. ",
"institutions_title": "... als Institution",
"institutions_text": "Wenn Sie als Museum bei museum-digital mitmachen wollen, dann braucht es nur eine kurze Beschreibung, ein Foto und die \u00fcblichen Kontaktdaten des Museums. Danach wird das Museum in der passenden Instanz von museum-digital eingerichtet und es wird ein Nutzerkonto erstellt. Da museum-digital sehr intuitiv ist gen\u00fcgt meistens schon eine halbst\u00fcndige Telefonunterweisung um Objekte erfolgreich zu ver\u00f6ffentlichen.\r\n<\/p><p>\r\nRegionale Museumsverb\u00e4nde oder -beratungsstellen bieten aber auch ganzt\u00e4gige Veranstaltungen an, auf denen das Arbeiten mit museum-digital erl\u00e4utert wird. Meist sind diese Veranstaltungen mit praktischen \u00dcbungen verbunden. Fragen Sie ihren regionalen Museumsverband oder bei einem der Betreuer einer Instanz von museum-digital."
}
}

18
mdorg/de/people.json Normal file
View File

@ -0,0 +1,18 @@
{
"tlPeople": {
"pageDescription": "Profilseite von %s auf museum-digital.org",
"on": "Auf ",
"tel": "Tel.",
"email": "e-Mail",
"html_feed": "HTML",
"rss": "RSS",
"md_blog": "museum-digital blog",
"affiliation": "Organisation",
"blog_posts_by": "Beitr\u00e4ge von %s",
"overviewTitle": "Team :: museum-digital",
"overviewDescription": "museum-digital is people. Here you can some people from our core team.",
"overviewKeywords": "museum-digital, team, people",
"overviewListTitle": "Team",
"overviewListSummary": "museum-digital is - in effect - people. Here you can find a list of some of our core team members in random order."
}
}

31
mdorg/de/portals.json Normal file
View File

@ -0,0 +1,31 @@
{
"tlPortals": {
"pageTitle": "Portale :: museum-digital",
"pageDescription": "museum-digital ist in verschiedene, regionale Portale unterteilt. Hier k\u00f6nnen Sie eine Liste dieser Portale finden.",
"pageKeywords": "museum-digital, Portal, Museumsobjekte, Objekte, Zugang",
"portals_title": "Die verschiedenen Portale von Museum-Digital",
"portals_introduction": "museum-digital ist in seinen Ausspielungen (Instanzen des <a href=\"\/software\/frontend\">\"Haupt-Frontends\"<\/a>) regional strukturiert. <a href=\"\/about\">Ausgehend von Sachsen-Anhalt<\/a> wurden anfangs regionale Portale f\u00fcr die verschiedenen Regionen in Deutschland angelegt. Diese werden mittlerweile in einer automatisch erstellten deutschlandweiten Instanz zusammengef\u00fchrt, bestehen aber weiterhin. Internationale Instanzen sind nach L\u00e4ndern strukturiert.<\/p><p>Eine Besonderheit in dieser Struktur bilden die \u00f6ffentlichen Zusatz-Werkzeuge, der <a href=\"#themator\">Themator<\/a> und <a href=\"#mdTerm\">md:term<\/a>.",
"international_portals": "Internationale Portale",
"german_portals": "Regionale Portale in Deutschland",
"themator_title": "Themator: Themenportale",
"themator_introduction": "Der Themator ist ein Werkzeug, entwickelt um Museen und anderen Interessierten eine einfache und flexible M\u00f6glichkeit zur Erstellung digitaler Ausstellungen, Lehrmaterialien etc. zu geben. Da der Themator weitestgehend monolingual ist, existieren aktuell zwei verschiedene Instanzen:",
"md_term_title": "md:term: \u00d6ffentlicher Zugang zu den kontrollierten Vokabularen von museum-digital",
"md_term_introduction": "Von Anfang an benutzt museum-digital kontrollierte Vokabulare, um ein gemeinsames Tagging und Verkn\u00fcpfen von Objektdatens\u00e4tzen zu erm\u00f6glichen. Da unsere so erstellten kontrollierten Vokabulare (die mit anderen Normdatenrepositorien wie Wikidata und der <abbr title=\"Gemeinsame Normdatei\">GND<\/abbr>, dem AAT, geonames, LCSH, BNF, ... verkn\u00fcpft sind) eine nutzbringende Erg\u00e4nzung auch f\u00fcr andere sein k\u00f6nnen, haben wir md:term als \u00f6ffentlichen Lese-Zugang zu den kontrollierten Vokabularen entwickelt. Neben dem \"menschenlesbaren\" Vokabularbrowser bietet md:term <abbr title=\"JavaScript Object Notation\">JSON<\/abbr>- und <abbr title=\"Simple Knowledge Organization System\">SKOS<\/abbr>-Schnittstellen, um auch eine maschinelle Nutzung der Daten einfach zu erm\u00f6glichen.\r\n<\/p><p>\r\nAbgesehen von den museum-digital eigenen Vokabularen sind unter md:term auch einige externe, im Museumsbereich h\u00e4ufig verwendete Vokabularien zug\u00e4nglich gemacht, so z.B. die Hessische Systematik oder die Hornbostel-Sachs-Klassifikation, zu finden.",
"Germany": "Deutschland",
"Hungary": "Ungarn",
"Brazil": "Brasilien",
"Indonesia": "Indonesien",
"themator_in_german": "Themator in Deutsch",
"themator_in_hungarian": "Themator in Ungarisch",
"Austria": "\u00d6sterreich",
"hungarian_portals": "Regionale Portale in Ungarn",
"portals_in_serbia": "Regionale Portale in Serbien",
"portals_in_romania": "Regionale Portale in Rum\u00e4nien",
"portals_in_the_usa": "Regionale Portale in den USA",
"Worldwide": "Weltweit",
"about_resources": "Ressourcen",
"Switzerland": "Schweiz",
"portals_in_switzerland": "Regionale Portale in der Schweiz",
"portals_in_austria": "Regionale Portale in \u00d6sterreich"
}
}

9
mdorg/de/privacy.json Normal file
View File

File diff suppressed because one or more lines are too long

10
mdorg/de/resources.json Normal file
View File

@ -0,0 +1,10 @@
{
"tlResources": {
"pageTitle": "Resources :: museum-digital",
"pageDescription": "Here you can find resources on museum-digital specifically and those relevant to the digitization in museums in general.",
"pageKeywords": "museums, resources, materials",
"resources_title": "Resources",
"resources_introduction": "Relevant resources can be found here.",
"general": "General"
}
}

9
mdorg/de/resources_documents.json Normal file
View File

@ -0,0 +1,9 @@
{
"tlDocuments": {
"pageTitle": "Dokumente :: museum-digital",
"pageDescription": "Eine Auswahl hilfreicher Dokumente zur Museumsarbeit, besonders wo sie das Digitale ber\u00fchrt, ist hier zu finden.",
"pageKeywords": "Dokumente, Museen, Museumsarbeit, Digitalisierung, Inventarisierung",
"title": "Dokumente",
"introduction": "Eine Auswahl hilfreicher Dokumente zur Museumsarbeit, besonders wo sie das Digitale ber\u00fchrt, ist hier zu finden."
}
}

14
mdorg/de/resources_links.json Normal file
View File

@ -0,0 +1,14 @@
{
"tlLinks": {
"pageTitle": "Links :: museum-digital",
"pageDescription": "Eine Auswahl relevanter Links zur Dokumentation und Digitalisierung im Museum kann hier gefunden werden.",
"pageKeywords": "Links, Museen, Digitalisierung im Museum, Museumsportale",
"title": "Links",
"introduction": "Hier k\u00f6nnen Sie eine Auswahl interessanter Links finden.",
"museum_portals": "Andere Museumsportale (mit Objektfokus)",
"organizations": "Organisationen",
"name": "Name",
"country": "Land",
"description": "Beschreibung"
}
}

16
mdorg/de/software.json Normal file
View File

@ -0,0 +1,16 @@
{
"tlSoftware": {
"pageTitle": "Software :: museum-digital",
"pageDescription": "Bei museum-digital haben wir verschiedene Software-Anwendungen entwickelt, um die Digitalisierung im Museum zu erleichtern.",
"pageKeywords": "software, Museen, Museumsobjekte, Museumssoftware, museum-digital",
"software_title": "Software",
"software_introduction": "Bei museum-digital haben wir \u00fcber die Jahre verschiedene Anwendungen entwickelt, um unserem Ziel, einer einfachen und inklusiven Digitalisierung im Museum n\u00e4herzukommen. museum-digital wurde urspr\u00fcnglich zum Zwecke der digitalen Publikation von Objektdaten <a href=\"\/about\">gegr\u00fcndet<\/a>, und so entwickelten wir zuerst eine <a href=\"\/software\/frontend\">Ausgabeoberfl\u00e4che f\u00fcr Objektinformationen<\/a>.<\/p>\r\n<p>Da die urspr\u00fcngliche Eingabemethode - Museum erfasst die Daten lokal, sendet sie an Programmierer, Programmierer tr\u00e4gt sie in die Datenbank ein - bald nicht mehr zu stemmen war, wurde eine einfache Eingabeoberfl\u00e4che, <a href=\"\/software\/musdb\">musdb<\/a>, entwickelt. Einige Museen, die noch keine Inventarisierungsdatenbank, aber Erfahrung mit musdb hatten, begannen nach Inventarisierungsfunktionen zu fragen, und so \u00e4nderte sich der Anspruch von musdb: Statt einer Eingabeoberfl\u00e4che f\u00fcr eine Publikationsplatform, wurde es zum Inventarisierungswerkzeug mit Publikationsoption.<\/p>\r\n<p>Bald darauf begann die Frage nach einer M\u00f6glichkeit zur digitalen Erfassung von Geschichten dr\u00e4ngender zu werden. Museumsobjekte, die nicht in einen Kontext eingebettet sind, m\u00f6gen zwar interessant sein, aber auch das Einbetten der Objekte in einen gr\u00f6\u00dferen Zusammenhang ist eine zentrale Aufgabe von Museen. Als Reaktion auf diese Frage wurde der <a href=\"\/software\/themator\">Themator<\/a> als unabh\u00e4ngig von den vorherigen Werkzeugen laufendes Tool entwickelt.<\/p>\r\n<p>Eine fr\u00fche Richtungsentscheidung bei der Entwicklung der Ausgabe und von musdb war es, mit allen Museen einer Sprachversion gemeinsam kuratierte kontrollierte Vokabulare zu verwenden. Diese werden intern mit dem Normdaten-Kontroll-Tool <a href=\"\/software\/term_nodac\">nodac<\/a> bearbeitet. Da die Vokabulare zunehmend wuchsen und wachsen, und mittlerweile selbst eine nutzbringende Quelle auch f\u00fcr andere Anwendungen sein k\u00f6nnen, entwickelten <a href=\"\/software\/term_nodac\">md:term<\/a>, mit dem Nutzer die Vokabulare durchsuchen und maschinell auslesen k\u00f6nnen.",
"frontend_portal": "Ausgabe \/ Portale",
"musdb": "musdb",
"themator": "Themator",
"term_nodac": "md:term & nodac",
"resources": "Resourcen",
"in_blog": "Technik-bezogene Neuigkeiten in unserem Blog",
"third_party_tools": "Drittanwendungen"
}
}

9
mdorg/de/software_development_log.json Normal file
View File

@ -0,0 +1,9 @@
{
"tlDevLog": {
"pageTitle": "Entwicklungs-Log :: museum-digital",
"pageDescription": "Entwicklung von museum-digital",
"pageKeywords": "Software, museum-digital, Entwicklung",
"status": "Status",
"development_log": "Entwicklung von museum-digital"
}
}

44
mdorg/de/software_frontend.json Normal file
View File

@ -0,0 +1,44 @@
{
"tlFrontend": {
"pageTitle": "Die \"Ausgabe\" :: museum-digital",
"pageDescription": "museum-digitals vorrangiges Ziel ist die digitale Zug\u00e4nglichmachung von Museumsinformationen - besonders Objektinformationen. Dies geschieht prim\u00e4r mit der \"Ausgabe\".",
"pageKeywords": "Software, Museen, Museumsobjekte, Museumssoftware, Webportal",
"frontend_title": "Die \"Ausgabe\"",
"frontend_introduction": "museum-digital wurde gegr\u00fcndet, um Museumsobjekte im Netz zug\u00e4nglich zu machen. Das geht nicht ohne die entsprechende Software.<\/p> <p>So ist die \"Ausgabe\" die erste Anwendung, die im Rahmen von museum-digital geschrieben wurde. Mit ihr k\u00f6nnen Museen sich und ihre Objekte gemeinsam im Netz darstellen und durchsuchbar machen.<\/p> <p>Um ein umfassendes Bild der Museen und ihrer Objekte zu liefern, wurden seitdem vielf\u00e4ltige zus\u00e4tzliche Informationen anzeigbar gemacht. Einerseits sind dies Informationen zu Sammlungen, Objektgruppen, Ausstellungen und Veranstaltungen, andererseits eine Vielzahl von Optionen, um die Objekte zu verkn\u00fcpfen und zu visualisieren.",
"technical_title": "Technisches",
"design_principles_title": "Design",
"design_principles_text": "Die \"Ausgabe\" von museum-digital ist nach dem Prinzip gestaltet, dass auf jeder Seite nur einige wenige zentrale Elemente im Fokus stehen sollen, sodass ein einfaches Verst\u00e4ndnis der Inhalte erleichtert wird. Viele weitere Optionen bestehen f\u00fcr Power-User - von Visualisierungen bis zu einer in die Webseite eingebauten Kommandozeile. Diese sind allerdings \"versteckt\", etwa in einer Seitenspalte oder durch Tastenkombinationen, um die Benutzbarkeit der Seite f\u00fcr Erstbenutzer nicht einzuschr\u00e4nken.",
"api_title": "Schnittstellen",
"api_text": "Zur Ver\u00f6ffentlichung und Verf\u00fcgbarmachung z\u00e4hlt nicht nur das Erm\u00f6glichen der Betrachtung. Auch eigene Ideen mit den Daten umzusetzen geh\u00f6rt dazu. Entsprechend sind alle Informationen, die mit der \"Ausgabe\" von museum-digital ver\u00f6ffentlicht sind auch maschinell \u00fcber eine einfach zu benutzende <abbr title=\"JavaScript Object Notation\">JSON<\/abbr>-Schnittstelle auslesbar.<\/p> <p>Soweit sinnvoll, gibt die \"Ausgabe\" Informationen auch in passenden offenen Standardformaten aus: Objektinformationen k\u00f6nnen im <a href=\"http:\/\/www.lido-schema.org\/\"><abbr title=\"Lightweight Information Describing Objects\">LIDO<\/a>-Format<\/a> abgerufen werden, f\u00fcr Museumsinformationen stehen digitale Visitenkarten (<a href=\"https:\/\/de.wikipedia.org\/wiki\/VCard\">vCard<\/a>) und f\u00fcr Termine Kalender und Kalendereintr\u00e4ge im <a href=\"https:\/\/de.wikipedia.org\/wiki\/ICalendar\">iCalendar-Format<\/a> zur Verf\u00fcgung.",
"development_title": "Entwicklung",
"development_text": "Die Ausgabe von museum-digital basiert auf PHP8 und MySQL. F\u00fcr Visualisierungen kommt JavaScript zum Einsatz, auch unter Zuhilfenahme einer Reihe von Bibliotheken, die <a href=\"https:\/\/handbook.museum-digital.info\/?lan=de&q=Weiteres\/Dependencies\">hier<\/a> eingesehen werden k\u00f6nnen. F\u00fcr die Versionierung benutzen wir <a href=\"https:\/\/git-scm.com\/\">git<\/a>.",
"screenshots": "Screenshots",
"resources": "Resourcen",
"in_blog": "Neuigkeiten zur Entwicklung der Ausgabe im Blog",
"screenshot-startpage": "Startseite des deutschlandweiten Portals von museum-digital",
"extended_search_alt": "Erweiterte Sucheinstellungen in der Ausgabe von museum-digital",
"screenshot_extended_search": "Mithilfe der erweiterten Suche, k\u00f6nnen Benutzer exakte Abfragen formulieren.",
"screenshot_enriched_search_results_alt": "Angereicherte Ergebnisseiten im museum-digital Frontend",
"screenshot_enriched_search_results": "Such-Ergebnisseiten werden, so m\u00f6glich, mit Informationen aus den <a href='\/about\/terminology'>kontrollierten Vokabularen<\/a> angereichert.",
"in_handbook": "Handbuchseiten zur Ausgabe",
"api_link": "Kurze Einf\u00fchrung zur API",
"screenshot_timeline_alt": "Eine Timeline-Seite bei museum-digital",
"screenshot_timeline": "Die \"Ausgabe\" von museum-digital bietet eine Zeitleiste, mit der Suchergebnisse nach Zeit sortiert betrachtet werden k\u00f6nnen.",
"screenshot_oak_alt": "Eine Objekte-auf-Karte-Seite von museum-digital.",
"screenshot_oak": "Mit der \"Objekte-auf-Karte\"-Funktion k\u00f6nnen Benutzer interessante Objekte auf Basis ihres geographischen Hintergrunds finden.",
"screenshot_object_page_alt": "Eine Objektseite.",
"screenshot_object_page": "Eine Objektseite im Frontend von museum-digital.",
"screenshot_multilinguality_alt": "Mehrsprachigkeit im Frontend von museum-digital.",
"screenshot_multilinguality": "museum-digital ist mehrsprachig, und so k\u00f6nnen es auch die erfassten Eintr\u00e4ge sein. Die Navigationssprache und Eintragssprache k\u00f6nnen unabh\u00e4ngig voneinander ausgew\u00e4hlt werden.",
"screenshot_exhibition_tiles_alt": "Ausstellungs\u00fcbersichtsseite in der Ausgabe von museum-digital",
"screenshot_exhibition_tiles": "Eine Ausstellungs-\u00dcbersichts-Seite im Kachel-Modus.",
"screenshot_calendar_alt": "Kalender sind Verf\u00fcgbar auf den \u00dcbersichtsseiten f\u00fcr Ausstellungen und Veranstaltungen.",
"screenshot_calendar": "Kalender sind Verf\u00fcgbar auf den \u00dcbersichtsseiten f\u00fcr Ausstellungen und Veranstaltungen.",
"screenshot_graph_view_alt": "\"Graphenansicht\"",
"screenshot_graph_view": "Mit der \"Graphenansicht\" bietet sich Benutzern eine alternative Navigationsoption.",
"screenshot_command_line_alt": "Tastatursteuerung im Frontend von museum-digital.",
"screenshot_command_line": "Power-user k\u00f6nnen das Portal mithilfe der eingebauten Tastatursteuerung navigieren.",
"screenshot_compare_objects_alt": "Objekte vergleichen.",
"screenshot_compare_objects": "Objekte k\u00f6nnen mit einem anderen - vorher zum Vergleich vorgemerkten - Objekt verglichen werden."
}
}

45
mdorg/de/software_musdb.json Normal file
View File

@ -0,0 +1,45 @@
{
"tlMusdb": {
"pageTitle": "musdb :: museum-digital",
"pageDescription": "musdb ist unser Tool f\u00fcr Erfassung, Inventarisierung und Museumsmanagement.",
"pageKeywords": "musdb, Inventarisierung, Museumsmanagement, Museen, Software",
"musdb_title": "musdb",
"musdb_introduction": "musdb wurde urspr\u00fcnglich als Eingabetool zur \u00f6ffentlichen Seite entwickelt. Seitdem haben wir es zu einem vollst\u00e4ndigen Inventarisierungswerkzeug erweitert. Auch Funktionen zum Museumsmanagement sind vorhanden.<\/p>\r\n\r\n<p>Zentral ist dabei:<ul>\r\n\r\n<li>Weiterenwicklungen findet auf Wunsch und in R\u00fccksprache mit den Museen statt<\/li>\r\n<li>musdb wird kollaborativ entwickelt: Anpassungen f\u00fcr ein Museum stehen allen Museen zur Verf\u00fcgung<\/li>\r\n<li>mit musdb arbeitet man kollaborativ: die Vokabulare, die f\u00fcr Verkn\u00fcpfungen mit Personen, Orten, Zeiten und Schlagworten benutzt werden, werden von allen Museen im gleichen Sprachraum gemeinsam genutzt<\/li>\r\n<li>musdb ist auf eine einfache und intuitive Benutzung ausgelegt<\/li>\r\n<li>Hilfestellungen und Warnungen regen dazu an, nicht nur einzugeben, sondern qualitativ hochwertige Datens\u00e4tze zu erzeugen<\/li><\/ul>",
"technical_title": "Technisches",
"design_principles_title": "Design",
"design_principles_text": "musdb soll einfach und intuitiv zu benutzen sein. Es soll Spa\u00df machen. Das hei\u00dft, dass die Oberfl\u00e4che einen klaren Fokus auf den Haupt-Gegenstand der jeweiligen Seite bieten sollte. Um dieses Ziel zu erreichen besteht f\u00fcr Benutzer an vielen Stellen die M\u00f6glichkeit, sich Features an- und auszuschalten. Optionale Features (etwa die zur Generierung eines QR-Codes f\u00fcr Objektseiten, oder ein \"Inhaltsverzeichnis\" um auf einer l\u00e4ngeren Seite direkt zum richtigen Bereich zu springen) sind in einer Toolbox am Fensterrand untergebracht.<\/p>\r\n\r\n<p><i>Einfach<\/i> hei\u00dft aber auch, dass h\u00e4ufige Benutzer schnell - und auf die ihnen am meisten gelegene Art - arbeiten k\u00f6nnen. Daf\u00fcr bietet musdb eine Vielzahl an Hilfestellungen. Bei der folgenden Liste handelt es sich deshalb nur um eine Auswahl:<\/p>\r\n<ul>\r\n <li>Eine Anzeige, wieviele Buchstaben in einem Eingabefeld eingegeben sind und wieviele es mindestens und maximal sein k\u00f6nnen<\/li>\r\n <li>PuQi: Der Publikationsqualit\u00e4tsindex zeigt, wie sich die Angaben zum Objekt verbessern lassen<\/li>\r\n <li>Plausi: Mithilfe der kontrollierten Vokabulare kann musdb warnen, wenn Eingaben nicht plausibel sind (Beispiel: Eine Malerin kann ein Gem\u00e4lde nicht gemalt haben, bevor sie geboren wurde)<\/li>\r\n <li>Textbausteine erleichtern die schnelle Eingabe von gleichen Inhalten<\/li>\r\n<\/ul>\r\n<p>Alternativ zur \u00fcblichen Navigation mit der Maus erm\u00f6glicht musdb eine umfassende Steuerung per Tastatur und ein eigenes Kontextmen\u00fc.",
"development_title": "Entwicklung",
"development_text": "musdb basiert auf PHP8 und MySQL. Eine Reihe PHP- und JavaScript-Bibliotheken kommen zum Einsatz. Die Liste der verwendeten Bibliotheken kann <a href=\"https:\/\/handbook.museum-digital.info\/?lan=de&q=Weiteres\/Dependencies#2\">im Handbuch<\/a> gefunden werden.",
"screenshots": "Screenshots",
"resources": "Resourcen",
"in_handbook": "musdb im Handbuch",
"videos_and_screencasts": "Videos auf YouTube",
"in_blog": "Neuigkeiten zur Entwicklung von musdb im Blog",
"screenshot_dashboard_alt": "Dashboard \/ Standard-Startseite von musdb.",
"screenshot_dashboard": "Die Standard-Startseite von musdb ist ein benutzerdefinierbares Dashboard. Auch andere Seiten k\u00f6nnen vom Benutzer als Startseite eingestellt werden.",
"screenshot_batch_editing_alt": "Stapelverarbeitung in musdb.",
"screenshot_batch_editing": "musdb bietet Funktionalit\u00e4ten zur Stapelverarbeitung. Beispielsweise k\u00f6nnen Filtermengen gesammelt vertaggt oder ver\u00f6ffentlicht werden.",
"screenshot_xml_export_alt": "XML-Export",
"screenshot_xml_export": "Benutzer k\u00f6nnen ihre Daten in md:xml (einer einfachen Notation f\u00fcr die Informationen aller verf\u00fcgbaren Felder) und <a href='http:\/\/lido-schema.org'>LIDO<\/a> exportieren.",
"screenshot_backgrounds_alt": "Hintergrund-Recherche-Tool.",
"screenshot_backgrounds": "Im Bereich \"Hintergr\u00fcnde\" k\u00f6nnen Benutzer direkt in musdb in den kontrollierten Vokabularen recherchieren.",
"screenshot_find_an_export_alt": "\"Finde einen Exporten\": Benutzer verbinden.",
"screenshot_find_an_export": "Mit dem \"Finde einen Experten\"-Button k\u00f6nnen Benutzer andere finden, die zum gleichen Thema gearbeitet haben. Nur solche Benutzer, die dies explizit anschalten, werden hier aufgelistet.",
"screenshot_multilingual_alt": "Mehrsprachigkeit in musdb.",
"screenshot_multilingual": "musdb ist mehrsprachig und kann auch mit mehrsprachigen Eingaben arbeiten.",
"screenshot_navigation_alt": "Navigation von musdb.",
"screenshot_navigation": "Die Navigation gibt einen groben \u00dcberblick \u00fcber die verschiedenen Sektionen von musdb: Museen, Sammlungen, Objekte, Objektgruppen, Ausstellungen, und mehr.",
"screenshot_object_overview_alt": "Objekt\u00fcbersicht in musdb.",
"screenshot_object_overview": "Eine Objekt-\u00dcbersichtsseite im Bildermodus. In der rechten Sidebar werden verschiedene Option zur Suche und zum filterbasierten Export angeboten. Eine einfache Listenansicht ist ebenfalls verf\u00fcgbar.",
"screenshot_object_page_alt": "Objektseite",
"screenshot_object_page": "Die Hauptsektion der Objektseite. Oben k\u00f6nnen Basisinformationen zum Objekt eingegeben werden. Unten sind die Registerkarten f\u00fcr die Bearbeitung detaillierter Informationen zum Objekt sichtbar.",
"screenshot_record_history_alt": "Datensatzgeschichte eines Objektes.",
"screenshot_record_history": "Bearbeitungen an Objektdatens\u00e4tzen werden geloggt.",
"screenshot_provenance_research_alt": "Registerkarte: Provenienzrecherche.",
"screenshot_provenance_research": "Mit der Registerkarte Provenienzrecherche k\u00f6nnen detaillierte Reporte zu einer vordefinierten Auswahl von relevanten Themen gespeichert werden.",
"screenshot_restoration_alt": "Registerkarte: Restaurierung",
"screenshot_restoration": "Die Registerkarte Restauration bietet einerseits die Option, eine farbkodierte und schnell zu erfassende Zusammenfassung des Objektzustands zu notieren, andererseits detaillierte Reporte zu speichern.",
"screenshot_user_management_alt": "Benutzer- und Rechteverwaltung.",
"screenshot_user_management": "Museumsdirektoren k\u00f6nnen detaillierte Rechte- und Zugriffseinstellungen f\u00fcr die Benutzer ihres Museums vornehmen."
}
}

9
mdorg/de/software_term_nodac.json Normal file
View File

@ -0,0 +1,9 @@
{
"tlTermNodac": {
"pageTitle": "nodac & md:term :: museum-digital",
"pageDescription": "Bei museum-digital haben wir zwei Tools entwickelt um kontrolliertes Vokabular zu bearbeiten und sichtbar zu machen: nodac und md:term.",
"pageKeywords": "Software, Kontrolliertes Vokabular, Tagging",
"term_nodac_title": "Werkzeuge zur Begriffskontrolle bei museum-digital: nodac und md:term",
"term_nodac_introduction": "nodac ist der Name des zentralen Werkzeugs zur Korrektur, Anreicherung und Hierarchisierung der bei museum-digital kontrollierten Begriffe. Das nodac-Tool ist mehrsprachig und kann zur Kontrolle von Vokabularen in vielen Sprachen eingesetzt werden. Mit dem nodac-Tool k\u00f6nnen externe Vokabulare verwaltet werden, wie etwa die Hornbostel-Sachs-Systematik f\u00fcr Musikinstrumente oder die Hessische Systematik.<\/p>\r\n\r\n<p>Vor allem dient nodac aber der Bearbeitung der eigenen Vokabulare von museum-digital.\r\nAnreicherung und Hierarchisierung der von den Museen eingegebenen Begriffe aus den Bereichen Akteure (Personen etc), Geografika (Orte etc.), Zeiten und Schlagworte geschehen ausschlie\u00dflich im nodac-Tool durch die Normdatenredaktion - und sie geschehen zentral f\u00fcr jede Sprachvariante von museum-digital. \r\nF\u00fcr die teilnehmenden Museen soll alles m\u00f6glichst einfach sein, deshalb kann jedes Museum beispielsweise frei Schlagworte zu seinen Objekten vergeben. Den Rest, also in diesem Falle eine Definition des Schlagwortes, eine Anreicherung mit Verkn\u00fcpfungen zu allgemein verwendeten Normdatenrepositorien (GND, AAT, geonames, ...) sowie die Hierarchiebildung \u00fcbernimmt die Normdatenredaktion mithilfe von nodac.<\/p>\r\n\r\n<p>\r\nmd:term ist quasi das Gegenst\u00fcck zu nodac. Es ist der freie verwendbare Zugang zu den museum-digital eigenen Vokabularen aber auch zu vielen anderen Vokabularen. Querverweise zwischen den Vokabularen werden genauso angezeigt wie jeder Begriff in seiner Hierarchie \u00fcber <a href=\"https:\/\/en.wikipedia.org\/wiki\/Simple_Knowledge_Organization_System\"><abbr title=\"Simple Knowledge Organization System\">SKOS<\/abbr><\/a> und <abbr title=\"JavaScript Object Notation\">JSON<\/abbr> zug\u00e4nglich gemacht wird. Auf diese Weise - und insbesondere durch die spezielle API von md:term - ist es auch anderen Programmen als museum-digital m\u00f6glich, das hier gespeicherte Wissen nachzunutzen und zu inkorporieren."
}
}

15
mdorg/de/software_themator.json Normal file
View File

@ -0,0 +1,15 @@
{
"tlThemator": {
"pageTitle": "Themator :: museum-digital",
"pageDescription": "Der Themator ist museum-digitals Software f\u00fcr digitales Story-telling.",
"pageKeywords": "Software, Story-telling, Themen, Narrative, Digitale Ausstellungen",
"themator_title": "Der Themator - Digitales Story-Telling und digitale Ausstellungen",
"screenshots": "Screenshots",
"themator_introduction": "Der Themator ist museum-digitals Software f\u00fcr digitales Storytelling.<\/p>\r\n<p>Bald nachdem das <a href=\"\/software\/frontend\">Haupt-Frontend<\/a> f\u00fcr museum-digital programmiert und ver\u00f6ffentlicht war, wurde die Frage nach M\u00f6glichkeiten zur Einbettung der Objektinformationen in digitale Narrative h\u00e4ufiger gestellt. Als Antwort darauf begann die Entwicklung des Themators.<\/p>\r\n<p>Der Themator ist um <em>Themen<\/em> strukturiert, die anderen Themen \u00fcber- und\/oder untergeordnet sein k\u00f6nnen. Sie k\u00f6nnen mit Objekten (sowohl solchen, die nur im Themator erfasst wurden als auch solchen aus den verschiedenen <a href=\"\/about\/portals\">Portalen von museum-digital<\/a>), Literatureintr\u00e4gen, und mehr verkn\u00fcpft werden. Der Fokus auf Themen erm\u00f6glicht eine breite Reihe an Anwendungsf\u00e4llen im Bereich des digitalen Storytellings, besonders wo es mit Museumsobjekten in Ber\u00fchrung kommt. Einerseits kann der Themator f\u00fcr digitale Ausstellungen verwendet werden. Andererseits wurde er beispielsweise aber auch schon zur Erstellung von <a href=\"https:\/\/hu.museum-digital.org\/themator\/ausgabe\/showthema.php?m_tid=1&tid=1&ver=standalone\">Lehrmaterialien f\u00fcr die deutsche Minderheit in Ungarn<\/a> eingesetzt.<\/p>\r\n<p>Die Breite der m\u00f6glichen Anwendungsf\u00e4lle f\u00fchrte zur Entscheidung den Themator als komplett eigenst\u00e4ndiges Werkzeug zu gestalten. Er erm\u00f6glicht die Einbindung von Objekten aus verschiedenen Instanzen in ein und dasselbe Thema.",
"screenshot_overview_germany": "\u00dcbersicht der Themen in der deutschsprachigen Version",
"screenshot_topic_page": "Eine \"Themenseite\" im Themator",
"screenshot_exhibition_view": "Der Themator bietet eine Ausstellungsansicht, ein wenig wie eine Diavorf\u00fchrung",
"screenshot_linked_objects": "Liste der mit einem Thema verbundenen Objekte",
"screenshot_object_page": "Ansicht eines einzelnen Objektes. Neben jenen Objekten, die speziell f\u00fcr den Themator erfasst wurden, k\u00f6nnen auch Objekte eingebunden werden, die aus museum-digital kommen."
}
}

14
mdorg/de/software_third_party.json Normal file
View File

@ -0,0 +1,14 @@
{
"tlThirdParty": {
"pageTitle": "Drittanwendungen :: museum-digital",
"pageDescription": "Mithilfe der verschiedenen Programmierschnittstellen sind bereits eine Reihe von zus\u00e4tzlichen Anwendungen erstellt worden.",
"pageKeywords": "Software, Museumssoftware, API, Digitalisierung im Museum, Programmierschnittstellen",
"title": "Anwendungen auf Basis der API",
"introduction": "Mithilfe der verschiedenen Programmierschnittstellen sind bereits eine Reihe von zus\u00e4tzlichen Anwendungen erstellt worden. Diese sind prinzipiell unabh\u00e4ngig von museum-digital. Da sie trotzdem in der einen oder anderen Art mit museum-digital interagieren, sammeln wir an dieser Stelle kurze Beschreibungen von solchen Anwendungen, von denen wir wissen.",
"resources": "Resourcen",
"in_blog": "Neuigkeiten zu API-basierten Anwendungen im Blog",
"website": "Webseite",
"license_usage": "Lizenz \/ Nutzung",
"authors": "Autor(en)"
}
}

12
mdorg/de/statistics.json Normal file
View File

@ -0,0 +1,12 @@
{
"tlStatistics": {
"frontend": "Ausgabe \/ Portal",
"musdb": "musdb",
"themator": "Themator",
"noda": "md:term & nodac",
"others": "Weitere",
"Total": "Gesamt",
"Checked": "Gepr\u00fcft",
"users": "Benutzer"
}
}

11
mdorg/de/terminology.json Normal file
View File

@ -0,0 +1,11 @@
{
"tlTerminology": {
"pageTitle": "Terminologie bei museum-digital :: museum-digital",
"pageDescription": "Bei museum-digital nutzen wir kontrollierte Vokabulare um das Auffinden zu erleichtern. Hier beschreiben wir, wie wir dabei vorgehen.",
"pageKeywords": "Terminologie, Museen, Kontrolliertes Vokabular, Tagging",
"terminology_title": "Kontrollierte Vokabulare bei museum-digital",
"terminology_role_of_terminology": "F\u00fcr museum-digital sind kontrollierte Begriffe von zentraler Bedeutung. In vier verschiedenen Katalogen werden Akteure (Personen, Institutionen, ...) Geografika (Orte und Geb\u00e4ude), Zeiten (Zeitpunkte und Zeitr\u00e4ume) sowie Schlagworte erfasst. Die einzelnen Begriffe werden angereichert mit Definitionen und Verweisen auf externe kontrollierte Vokabulare (Wikipedia, GND, ULAN, RKD, MBL, LAGIS, geonames, TGN, AAT, LCSH, ...). Gleichzeitig werden die Begriffe in Hierarchien eingepasst. Dies hat den Vorteil, dass bei einer Suche nach einem \u00fcbergeordneten Begriff immer auch die Objekte zu den untergeordneten Begriffen gefunden werden. Eine Suche nach Kinderspielzeug findet so auch alle Schaukelpferde und eine Suche nach Fahrzeugen findet alle Automobile.",
"terminology_how_we_do_it": "Wie werden die Vokabulare kontrolliert",
"terminology_how_we_do_it_text": "Vokabulararbeit ist bei museum-digital zentralisiert. Alle Museen in allen Instanzen einer Sprachvariante von museum-digital arbeiten mit dem jeweils gleichen Set von kontrollierten Begriffen. Gr\u00fcndliche Vokabularbeit ist sehr zeitaufwendig sein, deshalb wurde versucht m\u00f6glichst viel davon den teilnehmenden Museen abzunehmen. Zentralisierte Vokabularbeit f\u00fchrt au\u00dferdem zu eindeutigeren Resultaten.\r\nF\u00fcr die Vokabulararbeit haben wir ein eigenes Tool, <a href=\"\/software\/term_nodac\">nodac<\/a>, entwickelt mit welchem viele Anreicherungen semi-automatisch durchgef\u00fchrt werden k\u00f6nnen und mit dem es einfach ist, die jeweiligen Hierarchien zu erzeugen. Mit diesem Tool lassen sich zudem Massenkorrekturen durchf\u00fchren. Aus freiwilligen Beitr\u00e4gen der Museen, mit Unterst\u00fctzung einiger Bundesl\u00e4nder, aus Projektmitteln und insbesondere durch ehrenamtlichen Einsatz wird die Normdatenarbeit von einem kleinem Team bewerkstelligt."
}
}

14
mdorg/en/about.json Normal file
View File

@ -0,0 +1,14 @@
{
"tlAbout": {
"pageTitle": "About museum-digital :: museum-digital",
"pageDescription": "Who or what is museum-digital? We are a project to further the digitization of museums and museum data.",
"pageKeywords": "Museums, Digitization, Community, Research",
"about_title": "About museum-digital",
"about_introduction": "Museum-digital is an initiative of museums. The initiative was founded in 2009. It was created to develop a process as simple as possible for publishing information on museums and their objects online. Starting with six participating museums in Saxony-Anhalt, Germany, there are now over 600, mainly in Germany and Hungary. The simple publication has been extended with additional forms of presentation, but a strong focus on a good inventory has become a central feature of museum-digital. At museum-digital, we work together to develop software aimed at making inventorization and digital publishing easy but high quality.",
"about_resources": "Resources",
"logos_caption": "Here you can find the different logos of museum-digital for downloading.",
"background_title": "Where Do We Come From - and Where Will We Go?",
"background_content": "In mid 2009, the AG Digitization of the State Museum Association gathered and founded museum-digital. It was May 2009, and the recently founded working group soon spread to research how long it takes to digitize an object. The data thus gathered provided the fodder for an initial writing of the frontend for museum-digital.",
"the_future": "museum-digital is always open for people to join. The development takes place as it is needed. Where ever there may be museums that join hands to use museum-digital, be it for publishing, inventory or both, they can do so. If needed, a new instance will be created or we can consider other ways of cooperation. Since we develop alongside the always changing needs of the community, there is no clear-cut roadmap for museum-digital in the time ahead."
}
}

10
mdorg/en/about_faq.json Normal file
View File

@ -0,0 +1,10 @@
{
"tlFaq": {
"how_to_join_question": "How can a museum join museum-digital?",
"how_to_join_answer": "To join museum-digital, contact the admin of your local instance of museum-digital. If there is no regional instance for where you are yet, please contact us using the contact page.",
"pageTitle": "Frequently Asked Questions",
"pageDescription": "Frequently Asked Questions about museum-digital.",
"pageKeywords": "FAQ, Frequently Asked Questions, museums, collections, inventorization",
"faq_title": "Frequently Asked Questions"
}
}

11
mdorg/en/about_presentations.json Normal file
View File

@ -0,0 +1,11 @@
{
"tlPresentations": {
"pageTitle": "Presentations :: museum-digital",
"pageDescription": "A list of presentations held about museum-digital, sometimes with slides, sometimes with a video.",
"pageKeywords": "museum-digital, presentation, talk, video, slides",
"presentations_title": "Presentations about museum-digital",
"presentations_introduction": "Over the years, a lot of presentations have been held about different aspects of museum-digital - be it the software, be it the community, or how both interact. Here you can find a selection of these talks. If available, video recordings and slides are linked.",
"date": "Date",
"open": "Open"
}
}

11
mdorg/en/about_publications.json Normal file
View File

@ -0,0 +1,11 @@
{
"tlPublications": {
"pageTitle": "Publications :: museum-digital",
"pageDescription": "This page features a list of publications about and based on museum-digital.",
"pageKeywords": "museum-digital, Research, Academy, Publications",
"publications_title": "Publications about museum-digital",
"publications_introduction": "Besides providing infrastructure, museum-digital's flexibility and non-profit nature invites experimentation and provides ample opportunities for research. Over the years, a number of publications have been published on or based on museum-digital. You can find a list of these publications below.",
"Rohde-Enslin2015": "PuQi - A Clever Way to Produce Better Data",
"Kopp-Sievers2015": "museum-digital - A Civil Society Project of Large and Small Museums"
}
}

11
mdorg/en/calendar.json Normal file
View File

@ -0,0 +1,11 @@
{
"tlCalendar": {
"dateformat": "Y-M-D",
"calendarPageTitle": "Calendar :: museum-digital",
"calendarPageDescription": "On this page you can find current events concerning museum-digital, e.g. seminars.",
"calendarPageKeywords": "museum-digital, Calendar, Events, Seminars",
"calendar_title": "Calendar",
"calendar_introduction": "On this page you can find current events concerning museum-digital, e.g. seminars.",
"attendees": "Attendees"
}
}

11
mdorg/en/contact.json Normal file
View File

@ -0,0 +1,11 @@
{
"tlContact": {
"pageTitle": "Contact :: museum-digital",
"pageDescription": "Get in touch with museum-digital.",
"pageKeywords": "Contact, museum-digital",
"contacts_title": "Contact",
"contacts_introduction": "\"museum-digital\" is a common undertaking of museums and their associations. You can contact us at:",
"e-mail": "e-Mail",
"impressum": "Imprint"
}
}

37
mdorg/en/dashboard.json Normal file
View File

@ -0,0 +1,37 @@
{
"tlDashboard": {
"pageTitle": "Dashboard :: museum-digital",
"pageDescription": "Facts, Figures, Benchmarks on museum-digital and it's various instances",
"pageKeywords": "museum-digital, Statistics, Graphs, Museums, Museum Digitization",
"dashboard": "Dashboard",
"dashboard_introduction": "Here you can find facts and figures documenting the development and growth of museum-digital.",
"in_the_database": "Entities in the Database",
"objects": "Objects",
"museums": "Museums",
"collections": "Collections",
"literature_entries": "Literature entries",
"exhibitions": "Exhibitions",
"appointments": "Events",
"user_accounts": "User accounts",
"images": "Images",
"visitor_stats": "Visitor Statistics",
"visitors_yesterday": "Visitors yesterday",
"visitors_this_month": "Visitors this month",
"controlled_vocabularies": "Controlled Vocabularies",
"popular_entries_in_german": "Popular German-language Entries",
"title_actors": "Actors",
"title_places": "Places",
"title_tags": "Tags",
"popular_entries_in_hungarian": "Popular Hungarian-language Entries",
"controlled_vocabularies_figcaption_german": "Controlled vocabularies in the German database<br\/>From left to right: People, Places, Times, Tags",
"controlled_vocabularies_figcaption_hungarian": "Controlled vocabularies in the Hungarian database<br\/>From left to right: People, Places, Times, Tags",
"was_founded": "museum-digital was founded on %s",
"is_days_old": "museum-digital is %s days old",
"avg_obj_desc_length": "An average object description is %s characters long",
"avg_puqi_value": "The average <a href=\"https:\/\/journals.uic.edu\/ojs\/index.php\/UC\/article\/download\/6218\/5067\">PuQi<\/a> score of all public objects is",
"development": "Development",
"git_commits_by_project_and_month": "Development interactions by project and month",
"quality": "Quality",
"popular_entries": "Popular Entries"
}
}

8
mdorg/en/errorPages.json Normal file
View File

@ -0,0 +1,8 @@
{
"tlErrors": {
"403_title": "Forbidden",
"403_text": "You are not allowed to access this page. Please refer to the navigation above to find all of our pages.",
"404_title": "Oops ... There's nothing here",
"404_text": "There is nothing to be found here. At the top of the page you can however find contents in the navigation bar."
}
}

10
mdorg/en/footer.json Normal file
View File

@ -0,0 +1,10 @@
{
"tlFooter": {
"contact": "Contact",
"impressum": "Imprint",
"privacy": "Privacy Policy",
"search": "Search",
"search_in_mdorg": "Search museum-digital.org",
"search_in_md": "Search for objects"
}
}

14
mdorg/en/home.json Normal file
View File

@ -0,0 +1,14 @@
{
"tlHome": {
"pageTitle": "museum-digital",
"pageDescription": "museum-digital is a community project for the digitization of museum and museum object information.",
"pageKeywords": "Museums, Digitization, Community, Research",
"opener_title": "Enabling Museums to Let the World in - the Way they Want",
"opener_text": "museum-digital is an initiative, it is a software suite, and it is a platform. In January 2009, museum workers from the German state of Saxony-Anhalt gathered at the <a href=\"https:\/\/st.museum-digital.de\/index.php?t=institution&instnr=6\">Kreismuseum Bitterfeld<\/a> to discuss digitization and agreed to go online together. This was the founding event of museum-digital. Even then it was clear: Going online and becoming visible can only be achieved together. Together, software was developed; together, the museums present themselves and their objects online. What started as a small group in Saxony-Anhalt has now grown into a community that transcends national and language borders.",
"community_title": "Collaboration and Mutual Aid",
"community_text": "Every museum has its possibilities and aims. At museum-digital, they work together. In contrast to other portals, museum-digital offers tools both for <a href=\"\/software\/frontend\">publishing<\/a> and <a href=\"\/software\/musdb\">indexing<\/a> object information. All museums of the instances using a common primary language are using a shared pool of controlled and enriched terms. Working on a centralized pool of <a href=\"\/about\/terminology\">controlled vocabularies<\/a> saves each museum a lot of time and helps to visualize links between information from the different museums. It is thus a central part of successfully publishing online.<\/p>\r\n<p>\r\n<!-- By establishing appropriate communication channels, museum-digital supports the direct contact among colleagues beyond museum borders. -->\r\nThe community is inclusive and open: every museum can participate, as the greatest treasures are often found at far-off places.\r\nBeing open for museums of all kinds and sizes is only possible by putting flexibility and simplicity first. These, together with giving each museum and user full control over their data are the main principles of museum-digital.",
"counter_text_museums": "Vom Ausgangspunkt in Sachsen-Anhalt aus wuchs und w\u00e4chst die Zahl der an museum-digital beteiligten Museen zun\u00e4chst naturgem\u00e4\u00df in Deutschland, dann vor allem in Ungarn und dann dar\u00fcber hinaus. Museum-digital versucht ohne hohe Kosten f\u00fcr \u00dcbersetzer m\u00f6glichst viele Sprachgrenzen zu \u00fcberwinden und eine internationale Community entstehen zu lassen.",
"counter_text_collections": "Egal in welcher Region der Erde: Museen fassen Objekte zu Sammlungen zusammen. Die Sammlungen sind dabei oft nach gleichen Gesichtspunkten gegliedert, ein ungarisches Museum kann ebenso eine historische Glassammlung haben wie ein deutsches Museum. F\u00fcr Forscher und andere Interessierte f\u00fchrt museum-digital an dieser Stelle Sammlungen mit gleichem Schwerpunkt zusammen.",
"counter_text_objects": "Als Grenzen, ob politisch, wirtschaftlich oder Sprachgrenzen haben sich im Laufe der Zeit verschoben, Kunst- und Kulturschaffende sind ein- und ausgewandert. Lange bevor die global vernetzte \u00d6konomie f\u00fcr eine internationale Verteilung von Gebrauchs- und Kunstgegenst\u00e4nden sorgte gab es einen regen Austausch und Handel. Im Ergebnis finden sich Objekte zur Geschichte einer Region dieser Erde auch in Museen ganz anderer Regionen. Museum-digital versucht einen zentralen Zugang zu solchen Objekten zu schaffen"
}
}

7
mdorg/en/impressum.json Normal file
View File

@ -0,0 +1,7 @@
{
"tlImpressum": {
"pageTitle": "Imprint",
"pageDescription": "Imprint of museum-digital.org",
"pageKeywords": "Imprint, museum-digital, museum-digital.org"
}
}

1
mdorg/en/join_us.json Normal file
View File

@ -0,0 +1 @@
[]

9
mdorg/en/mission.json Normal file
View File

@ -0,0 +1,9 @@
{
"tlMission": {
"pageTitle": "Mission and Vision :: museum-digital",
"pageDescription": "museum-digital is a project for the digitization of museum data. Here we declare our mission.",
"pageKeywords": "Museum-digital, Museums, Digitization, Mission Statement, Aims",
"missions_title": "Mission",
"missions_introduction": "Museums and their objects should be online! Museum-digital's aim is to create simple to use tools and an appropriate environment for this. Museums that use a different software for inventory can use museum-digital for publishing their data. For all other museums that may not yet have a dedicated inventory tool museum-digital offers appropriate tools.<\/p>\r\n\r\n<p>Museum-digital is a community: all participating museums can join the conversation on what the project should focus on, and how the software is to be developed further. By and by, infrastructure is set up to facilitate and develop the conversation about the digital and museums.<\/p>\r\n\r\n<p>An important principle of museum-digital is to respect existing structures."
}
}

32
mdorg/en/navigation.json Normal file
View File

@ -0,0 +1,32 @@
{
"tlNavigation": {
"logo_alt_attribute": "Logo of museum-digital",
"news": "News",
"about": "About",
"resources": "Resources",
"software": "Software",
"software_md_ausgabe": "Frontend\/Portal",
"software_musdb": "musdb",
"software_themator": "Themator",
"software_term_nodac": "md:term & nodac",
"portals": "Portals",
"terminology_work": "Terminology work",
"dashboard": "Dashboard",
"participate": "Participate",
"mission": "Mission",
"resources_links": "Links",
"resources_documents": "Documents",
"third_party": "Third Party Tools",
"publications": "Publications",
"api_based": "Third Party Tools",
"impressum": "Copyright",
"contact": "Contact",
"privacy": "Privacy",
"people": "People",
"calendar": "Calendar",
"development_log": "Development Log",
"faq": "Frequently Asked Questions",
"presentations": "Presentations",
"document_archive": "Document archive"
}
}

16
mdorg/en/participate.json Normal file
View File

@ -0,0 +1,16 @@
{
"tlParticipate": {
"pageTitle": "Become a part of museum-digital! :: museum-digital",
"pageDescription": "Museum-digital is a community project. Of course, we always welcome volunteers who are ready to help out!",
"pageKeywords": "Participation, Volunteering, Community",
"participate_title": "Becoming a part of museum-digital",
"participate_introduction": "Helping museum-digital is possible in a multitude of ways. Direct participation is mainly reserved for museums, but anybody can help greatly by providing meaningful information and comments.",
"individuals": "You can visit a single museum",
"individuals_title": "...alone or with a group",
"individuals_text": "You can help museums greatly by providing information and working with the museums. At the bottom of almost all object pages, there is a link \"Do you know more ...?\". By clicking on this line, you can directly provide e-mail feedback on the given object to the related museum. You may however also offer help to a museum in your area of expertise.",
"local_museum_title": "Helping Out at Your Local Museum",
"local_museum_text": "Many, if not most, museums welcome little more than a helping hand. ",
"institutions_title": "... as an Institution",
"institutions_text": "If your institution wants to join museum-digital, you only need a short description, a photo, and the usual contact information of the museum. The museum will then be entered into the appropriate instance of museum-digital and a user account for the museum will be set up. Our tools have shown to be sufficiently intuitive for half an hour of an introduction (via phone) to be sufficient for publishing an object.<\/p>\r\n\r\n<p>Regional museum associations often offer day-long seminars in which working with museum-digital is discussed in more detail. These events usually feature hands-on exercises. It may be fruitful to consult your regional museum association or the administrator of your region of museum-digital."
}
}

18
mdorg/en/people.json Normal file
View File

@ -0,0 +1,18 @@
{
"tlPeople": {
"pageDescription": "Profile page of %s at museum-digital",
"on": "On",
"tel": "Tel.",
"email": "e-Mail",
"html_feed": "HTML feed",
"rss": "RSS",
"md_blog": "museum-digital blog",
"affiliation": "Affiliation",
"blog_posts_by": "Blog Posts by %s",
"overviewTitle": "Team :: museum-digital",
"overviewDescription": "Museum-digital is people. Here you can learn about some people from our core team.",
"overviewKeywords": "Museum-digital, Team, People",
"overviewListTitle": "Team",
"overviewListSummary": "Museum-digital is - in effect - people. Here you can find a list of some of our core team members in random order."
}
}

31
mdorg/en/portals.json Normal file
View File

@ -0,0 +1,31 @@
{
"tlPortals": {
"pageTitle": "Portals :: museum-digital",
"pageDescription": "Museum-digital is represented on different, regional portals. Here is a list of them.",
"pageKeywords": "Museum-digital, Portals, Museum Objects, Access",
"portals_title": "The different portals of museum-digital",
"portals_introduction": "Museum-digital is composed of different portals. Most of them are regionally structured.",
"international_portals": "International Portals",
"german_portals": "Regional portals in Germany",
"themator_title": "Themator: Topical Portals",
"themator_introduction": "The themator is a tool we developed to enable museums and like-minded people to create digital exhibitions and - more generally - to easily engage in digital storytelling. As the themator is largely monolingual, we have set up different instances of it.",
"md_term_title": "md:term: The controlled vocabularies of museum-digital made accessible",
"md_term_introduction": "Around 2010, we started to use controlled vocabularies to facilitate the common tagging and interlinking of digitized objects. For a long time, these vocabularies were not accessible for any outside viewers. Since they may be a useful resource to some, we have since developed md:term as a public and hopefully easily accessible portal for our (and some other) controlled vocabularies.",
"Germany": "Germany",
"Hungary": "Hungary",
"Brazil": "Brazil",
"Indonesia": "Indonesia",
"themator_in_german": "Themator in German",
"themator_in_hungarian": "Themator in Hungarian",
"Austria": "Austria",
"hungarian_portals": "Hungarian Regional Portals",
"portals_in_serbia": "Regional Portals in Serbia",
"portals_in_romania": "Regional Portals in Romania",
"portals_in_the_usa": "Regional Portals in the USA",
"Worldwide": "Worldwide",
"about_resources": "Resources",
"Switzerland": "Switzerland",
"portals_in_switzerland": "Regional portals in Switzerland",
"portals_in_austria": "Regional portals in Austria"
}
}

9
mdorg/en/privacy.json Normal file
View File

File diff suppressed because one or more lines are too long

10
mdorg/en/resources.json Normal file
View File

@ -0,0 +1,10 @@
{
"tlResources": {
"pageTitle": "Resources :: museum-digital",
"pageDescription": "Here you can find specific resources on museum-digital and those relevant to the digitization in museums in general.",
"pageKeywords": "Museums, Resources, Materials",
"resources_title": "Resources",
"resources_introduction": "Relevant resources can be found here.",
"general": "General"
}
}

9
mdorg/en/resources_documents.json Normal file
View File

@ -0,0 +1,9 @@
{
"tlDocuments": {
"pageTitle": "museum-digital :: Resources",
"pageDescription": "A selection of helpful documents about museum work in general and specific digital museum work can be found here.",
"pageKeywords": "Documents, Museums, Museum Works, Digitization, Inventory",
"title": "Documents",
"introduction": "A selection of helpful documents about museum work in general and specific digital museum work can be found here."
}
}

14
mdorg/en/resources_links.json Normal file
View File

@ -0,0 +1,14 @@
{
"tlLinks": {
"pageTitle": "museum-digital :: Links",
"pageDescription": "A selection of relevant links about museum digitization can be found here.",
"pageKeywords": "Links, Museums, Digitization in Museums, Museum Portals",
"title": "Links",
"introduction": "Here you can find a list of interesting links.",
"museum_portals": "Other Museum (Object) Portals",
"organizations": "Organizations",
"name": "Name",
"country": "Country",
"description": "Description"
}
}

16
mdorg/en/software.json Normal file
View File

@ -0,0 +1,16 @@
{
"tlSoftware": {
"pageTitle": "Software :: museum-digital",
"pageDescription": "At museum-digital, we have developed a set of software solutions to aid different parts of museum (digitization) work.",
"pageKeywords": "Software, Museums, Museum Objects, Museum Software, museum-digital",
"software_title": "Software",
"software_introduction": "At museum-digital, we have developed a set of software solutions to facilitate an easy and inclusive process of digitization in museums. Originally, museum-digital was founded to publish object information online. We thus began by developing a <a href=\"\/software\/frontend\">public interface for viewing object information<\/a>.\r\n<\/p>\r\n<p>\r\nSince the original method of data input - the museums entered their data into their local database, sent it to the programmers, the programmers entered it to museum-digital - did not scale well, we then developed a simple online input interface, <a href=\"\/software\/musdb\">musdb<\/a>. Some museums, that did not yet have a dedicated database for inventorized data, but knew musdb well, began to ask additional inventory functionalities. And thus the approach of musdb changed: instead of being an input interface to a publication platform, it turned into an inventory tool with the option to publish.\r\n<\/p>\r\n<p>\r\nSoon after, requests for options to more thoroughly present digital narratives and stories became more frequent. While museum objects may be interesting by themselves, it is also a central task of museums to contextualize them. As a reaction to these requests, we created the <a href=\"\/software\/themator\">Themator<\/a> as an independent tool for writing and publishing stories online.\r\n<\/p>\r\n<p>\r\nEarly on, when developing the main frontend and musdb, we decided to use controlled vocabularies for all databases of a given language. Internally, we use our \"norm data control tool\" <a href=\"\/software\/term_nodac\">nodac<\/a> for curating these. Since the vocabularies have grown considerably since, and have become a useful resource on their own by now, we have also developed a searchable frontend for these, <a href=\"\/software\/term_nodac\">md:term<\/a>.",
"frontend_portal": "Frontend\/Portals",
"musdb": "musdb",
"themator": "Themator",
"term_nodac": "md:term & nodac",
"resources": "Resources",
"in_blog": "Tech-Related News in our Blog",
"third_party_tools": "Third party tools"
}
}

9
mdorg/en/software_development_log.json Normal file
View File

@ -0,0 +1,9 @@
{
"tlDevLog": {
"pageTitle": "Development Log :: museum-digital",
"pageDescription": "Log of development on museum-digital",
"pageKeywords": "Software, museum-digital, Development",
"status": "Status",
"development_log": "Development Log"
}
}

44
mdorg/en/software_frontend.json Normal file
View File

@ -0,0 +1,44 @@
{
"tlFrontend": {
"pageTitle": "The Main Frontend\/Portal Software :: museum-digital",
"pageDescription": "Most of the work museum-digital does focuses on bringing museums online. We do so mainly using our main frontend\/portal software.",
"pageKeywords": "Software, Museums, Museum Objects, Museum Software, Exhibitions, Web Portal",
"frontend_title": "The Main Frontend of museum-digital",
"frontend_introduction": "museum-digital was founded to publish museum object information online. That's not possible without the right software.<\/p>\r\n<p>The \"frontend\" is thus the first application, that was developed at museum-digital. With it, museums can join together to present themselves and their objects online.<\/p>\r\n<p>To offer a comprehensive glimpse at the museums and their objects, a variety of additional information has been made presentable since. On the one hand, museums can now add information on their collections, object groups, exhibitions, and events. On the other, a number of options for linking and visualizing information have been added.",
"technical_title": "Technical Information",
"design_principles_title": "Focus - Design Principles",
"design_principles_text": "\"The \"frontend\" of museum-digital is primarily designed to always offer a clear focus on whichever information is central to a given page or section. This allows for easy understanding. A lot of additional options exist for power users - from visualizations to a command line menu embedded into the website. These are however \"hidden\" in sidebars or only accessible through keyboard shortcuts, so that they don't irritate first-time users.",
"api_title": "API(s)",
"api_text": "Publishing and making things accessible doesn't only mean making it possible to view something. It also means enabling people to use data to realize their own ideas. Accordingly, all information that is published using the \"frontend\" of museum-digital is also accessible in a machine-readable way via our <abbr title=\"JavaScript Object Notation\">JSON<\/abbr> API.<\/p><p>As much as possible, the \"frontend\" provides information in open standards as well: object information can be accessed in <a href=\"http:\/\/network.icom.museum\/cidoc\/working-groups\/lido\/what-is-lido\/\">LIDO<\/a>, information about museums can be downloaded as electronic business cards (<a href=\"https:\/\/de.wikipedia.org\/wiki\/VCard\">vCard<\/a>), and calendar information such as exhibitions can be integrated with calendar tools using the <a href=\"https:\/\/de.wikipedia.org\/wiki\/ICalendar\">iCalendar<\/a> standard.",
"development_title": "Development",
"development_text": "The \"frontend\" of museum-digital is built using PHP8 and MySQL. JavaScript is used for interactive features and visualizations. A list of the used libraries can be found <a href=\"https:\/\/handbook.museum-digital.info\/?lan=de&q=Weiteres\/Dependencies\">here<\/a>. We use <a href=\"https:\/\/git-scm.com\/\">git<\/a> for version control.",
"screenshots": "Screenshots",
"resources": "Resources",
"in_blog": "News About the Frontend in the Blog",
"screenshot-startpage": "Start page of the German national portal of museum-digital.",
"extended_search_alt": "Extended search page in the museum-digital frontend.",
"screenshot_extended_search": "Using the extended search settings, users can define exact searches.",
"screenshot_enriched_search_results_alt": "Enriched search results in the museum-digital frontend",
"screenshot_enriched_search_results": "Search result pages are enriched based on data from our <a href='\/about\/terminology'>controlled vocabularies<\/a>.",
"in_handbook": "Handbook pages about the frontend",
"api_link": "Short introduction to the API",
"screenshot_timeline_alt": "A timeline page in museum-digital.",
"screenshot_timeline": "The museum-digital frontend offers a timeline, for viewing search results sorted by their relations to time.",
"screenshot_oak_alt": "Objects on map pages in museum-digital.",
"screenshot_oak": "Using the \"objects on map\" pages, users can find interesting objects based on their geographical background.",
"screenshot_object_page_alt": "An object page.",
"screenshot_object_page": "An object page in the frontend of museum-digital.",
"screenshot_multilinguality_alt": "Multilingualism in the museum-digital frontend.",
"screenshot_multilinguality": "museum-digital is multilingual, and so, too, can be the displayed entries. The navigation language and the record language can be switched independent of each other.",
"screenshot_exhibition_tiles_alt": "Exhibition overview page in the museum-digital frontend",
"screenshot_exhibition_tiles": "The exhibition overview page in tiles mode.",
"screenshot_calendar_alt": "Calendars are available for exhibitions and events.",
"screenshot_calendar": "Calendars are available for exhibitions and events.",
"screenshot_graph_view_alt": "\"Graph view\"",
"screenshot_graph_view": "The \"graph view\" offers users an alternative option for navigating the portal.",
"screenshot_command_line_alt": "Keyboard control of the museum-digital frontend.",
"screenshot_command_line": "Power users can navigate the portal using their keyboard through an emacs-inspired interface.",
"screenshot_compare_objects_alt": "Comparing obects",
"screenshot_compare_objects": "Two objects can be compared with each other"
}
}

45
mdorg/en/software_musdb.json Normal file
View File

@ -0,0 +1,45 @@
{
"tlMusdb": {
"pageTitle": "musdb :: museum-digital",
"pageDescription": "musdb is museum-digital's tool for indexing and creating inventories. It has in many ways developed into a more general museum-management tool.",
"pageKeywords": "musdb, Museum Management, Inventory, Software",
"musdb_title": "musdb",
"musdb_introduction": "Musdb is museum-digital's tool for indexing and creating inventories. Originally developed for recording objects to be published only, it has since developed into a full-featured inventory and museum management solution.<\/p>\r\n<p>Central to the development of musdb are:\r\n<ul>\r\n<li>musdb is developed based on requests by and communication with the museums using it<\/li>\r\n<li>musdb is made with collaboration in mind: New features and fixes are available to all museums<\/li>\r\n<li>using musdb means working collaboratively: the controlled vocabularies, that are used for linking people, times, places, and tags, are used together by all museums of a given language<\/li>\r\n<li>working with musdb should be as easy and intuitive as possible<\/li>\r\n<li>Tips and warnings are given to not just enter data, but to create high quality data<\/li>\r\n<\/ul>",
"technical_title": "Technical Information",
"design_principles_title": "Design Principles",
"design_principles_text": "Musdb should be easy and intuitive to use. It should be fun to use. On the one hand, this means that the design should give a clear focus to the main subject of a given page. To reach this aim, options exist to toggle many features on or off. Optional features (like generating QR codes for object pages or a table of contents to directly jump to the wanted section of a page) are available in a toolbox on the left border of the window.<\/p>\r\n\r\n<p>But <i>easy<\/i> and <i>intuitive<\/i> also means that power users can work efficiently in whatever way suits them best. Musdb offers a variety of aids for this. A selection of these are:<\/p>\r\n\r\n<p>\r\n<ul>\r\n<li>Clicking into a field, users can see how many characters have been entered, how many are required, and how many are allowed at max.<\/li>\r\n<li>PuQi: the \"Publication Quality Index\" shows, how object information can be enhanced<\/li>\r\n<li>Plausi: using the controlled vocabularies, musdb can warn about implausible entries (e.g. a painter cannot have painted a painting before she was born)<\/li>\r\n<li>Text blocks provide for a quick entry of similar contents<\/li>\r\n<\/ul>",
"development_title": "Development",
"development_text": "Musdb is based on PHP8 and MySQL. A number of PHP and JavaScript libraries are used, a list of which can be found <a href=\"https:\/\/handbook.museum-digital.info\/?lan=de&q=Weiteres\/Dependencies#2\">in the handbook<\/a>.",
"screenshots": "Screenshots",
"resources": "Resources",
"in_handbook": "Documentation for musdb",
"videos_and_screencasts": "Videos on YouTube",
"in_blog": "News About the Development of musdb",
"screenshot_dashboard_alt": "Dashboard\/Default startpage of musdb.",
"screenshot_dashboard": "The default start page is a customizable dashboard. Other start pages can be selected by the user.",
"screenshot_batch_editing_alt": "Batch editing in musdb.",
"screenshot_batch_editing": "Musdb features batch editing functionalities for batch publishing or tagging.",
"screenshot_xml_export_alt": "XML export",
"screenshot_xml_export": "Users can export their data in our own md:xml (a simple notation featuring all available fields) and <a href='http:\/\/lido-schema.org'>LIDO<\/a>.",
"screenshot_backgrounds_alt": "Background research tool.",
"screenshot_backgrounds": "Using the \"backgrounds\" section, users can browse the controlled vocabularies directly from musdb.",
"screenshot_find_an_export_alt": "Find an expert: Connecting users.",
"screenshot_find_an_export": "Using the \"Find an Export\" button, users can find other users who have done much work on a given topic. Still, every user can decide if they want to let others find them through this tool or not.",
"screenshot_multilingual_alt": "Multilingual usage of musdb.",
"screenshot_multilingual": "Musdb is multilingual and it can handle multilingual inputs.",
"screenshot_navigation_alt": "Navigation of musdb.",
"screenshot_navigation": "The navigation gives a rough overview over different sections of musdb: Museums, Collections, Objects, Object Groups, Exhibitions, etc.",
"screenshot_object_overview_alt": "Object overview page.",
"screenshot_object_overview": "An object overview page in image mode. The sidebar on the right offers search and filter-based exporting and batch editing functionalities. A simple list view is also available.",
"screenshot_object_page_alt": "Object page",
"screenshot_object_page": "The main section of an object page. At the top, most basic information on the object can be entered. At the bottom, the tabbed menu for managing detailed information on the object can be seen.",
"screenshot_record_history_alt": "Record history of an object.",
"screenshot_record_history": "Edits to an object are logged. If the user who previously edited the object set up their user profile, new users who see the logs can get to know others from the museum through the logs.",
"screenshot_provenance_research_alt": "Provenance research tab",
"screenshot_provenance_research": "Using the provenance research tab, detailed reports on a predefined set of critical issues can be recorded.",
"screenshot_restoration_alt": "Restoration tab on a musdb object page",
"screenshot_restoration": "The restoration tab of an object page offers options for color-coded and easily accessible notes towards the top of the section, detailed ones on the bottom.",
"screenshot_user_management_alt": "User management and user rights section",
"screenshot_user_management": "Museum directors and regional administrators set detailed permissions for what users can edit or view."
}
}

9
mdorg/en/software_term_nodac.json Normal file
View File

@ -0,0 +1,9 @@
{
"tlTermNodac": {
"pageTitle": "Nodac & md:term :: museum-digital",
"pageDescription": "At museum-digital we build two tools for managing and displaying controlled vocabularies: md:term and nodac.",
"pageKeywords": "Software, Controlled Vocabularies, Subject Headings",
"term_nodac_title": "Our Tools for Managing Controlled Vocabularies: nodac and md:term",
"term_nodac_introduction": "nodac is the name of our tool for correcting, enriching, and stratifying controlled vocabularies at museum-digital. Nodac is multilingual and can be used for controlling vocabularies in different languages. Using nodac, external vocabularies can be managed as well: for example the Hornbostel-Sachs-Systematik for musical instruments or the Hessische Systematik. The primary use of the tool remains, however, the curation of the museum-digital's own controlled vocabularies. It is the dedicated place for in-depth enrichment of terms from the domains of \"actors\" (people and institutions), geographic places, times, and tags. These are controlled centrally for a given language by the <i>norm data editors<\/i>. Each participating museum can however submit requests for changes.<\/p>\r\n\r\n<p>While it is the dedicated aim of museum-digital to make entering and linking - for example - a tag as easy as possible for the museums, further edits like providing a definition of the term and linking it with other controlled vocabularies are taken over by the <i>norm data editors<\/i>. It thus becomes a background task, that does however remain central to the success of the whole endeavor. It is only because we keep curated controlled vocabularies, that we can generate correct timelines or place objects on maps in any meaningful way.<\/p>\r\n\r\n<p>md:term is the public equivalent of nodac. It provides for public, structured access to our own vocabularies and a number of external ones. Besides making the vocabularies browse-able, it offers <a href=\"https:\/\/en.wikipedia.org\/wiki\/Simple_Knowledge_Organization_System\"><abbr title=\"Simple Knowledge Organization System\">SKOS<\/abbr><\/a> and <abbr title=\"JavaScript Object Notation\">JSON<\/abbr> interfaces. In this way, it provides access for other developers and projects to creatively use and incorporate our controlled vocabularies."
}
}

15
mdorg/en/software_themator.json Normal file
View File

@ -0,0 +1,15 @@
{
"tlThemator": {
"pageTitle": "Themator :: museum-digital",
"pageDescription": "The Themator is museum-digital's solution for digital story-telling.",
"pageKeywords": "Software, Story Telling, Topics, Stories, Narrative, Exhibitions",
"themator_title": "The Themator - A Tool for Online Storytelling and Digital Exhibitions",
"screenshots": "Screenshots",
"themator_introduction": "The Themator is museum-digital's solution for digital story-telling.<\/p><p>After setting up the <a href=\"\/software\/frontend\">main frontend<\/a> for museum-digital, questions for how to embed the thus published objects in online narratives soon arose. To answer this demand, the development of the Themator began.<\/p><p>The Themator is structured around topics, which can be super- or subordinate to other topics and which can be associated with objects (both those entered only in the Themator and those published in any of the <a href=\"\/about\/portals\">main portals of museum-digital<\/a>), literature entries, and more. This focus on <em>topics<\/em> provides for a broad range of possible uses in the field of digital storytelling, especially where it relates to museum objects. On the one hand, the Themator can be used for creating digital exhibitions. On the other, it has been used to create learning materials (e.g. <a href=\"https:\/\/hu.museum-digital.org\/themator\/ausgabe\/showthema.php?m_tid=1&tid=1&ver=standalone\">for teaching in German minority schools in Hungary<\/a>). This, combined with the need to be able to embed objects from the different instances in the same topic, led us to design the Themator as a tool completely independent from the main instances.",
"screenshot_overview_germany": "Overview of topics available in the German-language Themator",
"screenshot_topic_page": "A topic page in the Themator",
"screenshot_exhibition_view": "The Themator features a slideshow-like \"exhibition view\"",
"screenshot_linked_objects": "List of objects linked to a topic",
"screenshot_object_page": "Page for a single object. Besides those entered only in the Themator, objects can also be embedded from museum-digital"
}
}

14
mdorg/en/software_third_party.json Normal file
View File

@ -0,0 +1,14 @@
{
"tlThirdParty": {
"pageTitle": "Third Party Tools :: museum-digital",
"pageDescription": "Based on the APIs of museum-digital, a number of third party tools have been written. Here you can find some of them.",
"pageKeywords": "Software, Museum Software, API, Digitization in Museums",
"title": "Third Party Tools",
"introduction": "Using the different APIs of museum-digital, a number of additional tools have been written. These are in principle independent of museum-digital, but since they interact with or are based on museum-digital in some way, we collect brief introductions to those we know of here.",
"resources": "Resources",
"in_blog": "News About API-Based Tools in our Blog",
"website": "Website",
"license_usage": "License\/Usage",
"authors": "Author(s)"
}
}

12
mdorg/en/statistics.json Normal file
View File

@ -0,0 +1,12 @@
{
"tlStatistics": {
"frontend": "Frontend",
"musdb": "musdb",
"themator": "Themator",
"noda": "md:term \/ nodac",
"others": "Others",
"Total": "Total",
"Checked": "Checked",
"users": "Users"
}
}

11
mdorg/en/terminology.json Normal file
View File

@ -0,0 +1,11 @@
{
"tlTerminology": {
"pageTitle": "Terminology Work at museum-digital :: museum-digital",
"pageDescription": "At museum-digital we use controlled vocabularies, to enrich the users' experience. Here we describe, how they are handled.",
"pageKeywords": "Terminology, Museums, Controlled Vocabularies, Tagging",
"terminology_title": "Controlled Vocabularies at museum-digital",
"terminology_role_of_terminology": "Controlled vocabularies are a central issue to museum-digital. Sorted into four catagories (Persons and Institutions, Geographical Places, Times, and Keywords), terms are enriched with definitions and links to external controlled vocabularies and services (Wikipedia, GND, ULAN, RKD, MBL, LAGIS, geonames, TGN, AAT, LCSH, ...). At the same time, they are categorized hierarchically. This provides for the possibility to return objects linked to subordinate terms to searches for a given superordinate term. A search for \"vehicle\" thus returns any object linked to \"car\" as well.",
"terminology_how_we_do_it": "How are the Vocabularies Controlled?",
"terminology_how_we_do_it_text": "<p>The curation of controlled vocabularies at museum-digital takes place in a centralized manner. All museums of all instances of a given primary language work together to create a common database of controlled terms. Since curating controlled vocabularies is time consuming, we try to reduce the participating museums' workload in this regard as much as possible. Besides, a centralized curation of controlled vocabularies leads to more uniform results.<\/p><p>To ease the curation, we have developed a tool, <a href=\"\/software\/term_nodac\">\"nodac\"<\/a>, which automatizes much of the enrichment work and offers a simple interface for positioning terms hierarchically. With this tool, norm data editors, can also use batch editing functionalities for enhancing the controlled vocabularies.<\/p><p>The curation of controlled vocabularies is thus a joint effort of the participating museums, direct volunteering, and support by a number of state governments, led by a small team of \"norm data editors\".<\/p>"
}
}

14
mdorg/hu/about.json Normal file
View File

@ -0,0 +1,14 @@
{
"tlAbout": {
"pageTitle": "museum-digital :: About museum-digital",
"pageDescription": "Who or what is museum-digital? We are a project to further the digitization of museums and museum data.",
"pageKeywords": "museums, digitization, community, research",
"about_title": "About museum-digital",
"about_introduction": "museum-digital is an initiative of museums. The initiative was founded in 2009. It was created to develop a process as simple as possible for publishing information on museums and their objects online. Starting with six participating museums in Saxony-Anhalt, Germany, there are now over 600, mainly in Germany and Hungary. The simple publication has been extended with additional forms of presentation, but a strong focus on a good inventorization has become a central feature of museum-digital. At museum-digital, we work together to develop software aimed at making inventorization and digital publishing easy but high quality.",
"about_resources": "Resources",
"logos_caption": "Here you can find the different logos of museum-digital for downloading.",
"background_title": "Where Do We Come From - and Where Will We Go?",
"background_content": "In mid 2009, the AG Digitalisierung of the Landesmuseumsverband gathered and founded museum-digital. It was May 2009, and the recently founded working group soon spread to research how long it takes to digitize an object. The data thus gathered provided the fodder for an initial writing of the frontend for museum-digital.",
"the_future": "museum-digital is always open for people to join. The development takes place as it is needed. Where ever there may be museums that join hands to use museum-digital, be it for publishing, inventorization or both, they can do so. If needed, a new instance will be created or we can consider other ways of cooperation. Since we develop along the always changing needs of the community, there is no clear-cut roadmap for museum-digital in the time ahead."
}
}

10
mdorg/hu/about_faq.json Normal file
View File

@ -0,0 +1,10 @@
{
"tlFaq": {
"how_to_join_question": "How can a museum join museum-digital?",
"how_to_join_answer": "To join museum-digital, contact the admin of your local instance of museum-digital. If there is no regional instance for where you are yet, please contact us using the contact page.",
"pageTitle": "Frequently Asked Questions",
"pageDescription": "Frequently Asked Questions about museum-digital.",
"pageKeywords": "FAQ, Frequently Asked Questions, museums, collections, inventorization",
"faq_title": "Frequently Asked Questions"
}
}

11
mdorg/hu/about_presentations.json Normal file
View File

@ -0,0 +1,11 @@
{
"tlPresentations": {
"pageTitle": "Presentations :: museum-digital",
"pageDescription": "A list of presentations held about museum-digital, sometimes with slides, sometimes with a video.",
"pageKeywords": "museum-digital, presentation, talk, video, slides",
"presentations_title": "Presentations about museum-digital",
"presentations_introduction": "Over the years, a lot of presentations have been held about different aspects of museum-digital - be it the software, be it the community, or how both interact. Here you can find a selection of these talks. If available, video recordings and slides are linked.",
"date": "Date",
"open": "Open"
}
}

11
mdorg/hu/about_publications.json Normal file
View File

@ -0,0 +1,11 @@
{
"tlPublications": {
"pageTitle": "Publications",
"pageDescription": "This page features a list of publications on museum-digital.",
"pageKeywords": "museum-digital, research, academy, publications",
"publications_title": "Publications about museum-digital",
"publications_introduction": "Besides providing infrastructure, museum-digital's flexibility and non-profit nature invites experimentation and provides ample opportunities for research. Over the years, a number of publications have been published on or based on museum-digital.",
"Rohde-Enslin2015": "PuQi - Ein Cleverer Weg bessere Daten zu produzieren",
"Kopp-Sievers2015": "museum-digital - A Civil Society Project of Large and Small Museums"
}
}

11
mdorg/hu/calendar.json Normal file
View File

@ -0,0 +1,11 @@
{
"tlCalendar": {
"dateformat": "Y-m-d",
"calendarPageTitle": "Calendar :: museum-digital",
"calendarPageDescription": "On this page you can find current events concerning museum-digital, e.g. seminars.",
"calendarPageKeywords": "museum-digital, calendar, events, seminars",
"calendar_title": "Calendar",
"calendar_introduction": "On this page you can find current events concerning museum-digital, e.g. seminars.",
"attendees": "Attendees"
}
}

11
mdorg/hu/contact.json Normal file
View File

@ -0,0 +1,11 @@
{
"tlContact": {
"pageTitle": "museum-digital :: Contact",
"pageDescription": "Get in touch with museum-digital.",
"pageKeywords": "contact, museum-digital",
"contacts_title": "Contact",
"contacts_introduction": "\"museum-digital\" is a common undertaking of museums and their associations. You can contact us at:",
"e-mail": "e-Mail",
"impressum": "Impressum"
}
}

37
mdorg/hu/dashboard.json Normal file
View File

@ -0,0 +1,37 @@
{
"tlDashboard": {
"pageTitle": "museum-digital :: Dashboard",
"pageDescription": "Facts, Figures, Benchmarks on museum-digital and it's various instances",
"pageKeywords": "museum-digital, statistics, graphs, museums, museum digitization",
"dashboard": "Dashboard",
"dashboard_introduction": "Here you can find facts and figures documenting the development and growth of museum-digital.",
"in_the_database": "Entities in the Database",
"objects": "objects",
"museums": "museums",
"collections": "collections",
"literature_entries": "literature entries",
"exhibitions": "exhibitions",
"appointments": "events",
"user_accounts": "user accounts",
"images": "images",
"visitor_stats": "Visitor Statistics",
"visitors_yesterday": "visitors yesterday",
"visitors_this_month": "visitors this month",
"controlled_vocabularies": "Controlled Vocabularies",
"popular_entries_in_german": "Popular German-language Entries",
"title_actors": "Actors",
"title_places": "Places",
"title_tags": "Tags",
"popular_entries_in_hungarian": "Popular Hungarian-language Entries",
"controlled_vocabularies_figcaption_german": "Controlled vocabularies in the German database<br\/>From left to right: people, places, times, tags",
"controlled_vocabularies_figcaption_hungarian": "Controlled vocabularies in the Hungarian database<br\/>From left to right: people, places, times, tags",
"was_founded": "museum-digital was founded on %s",
"is_days_old": "museum-digital is %s days old",
"avg_obj_desc_length": "An average object description is %s characters long",
"avg_puqi_value": "The average <a href=\"https:\/\/journals.uic.edu\/ojs\/index.php\/UC\/article\/download\/6218\/5067\">PuQi<\/a> score of all public objects is",
"development": "Development",
"git_commits_by_project_and_month": "Development interactions by project and month",
"quality": "Quality",
"popular_entries": "Popular Entries"
}
}

8
mdorg/hu/errorPages.json Normal file
View File

@ -0,0 +1,8 @@
{
"tlErrors": {
"403_title": "Forbidden",
"403_text": "You are not allowed to access this page. Please refer to the navigation above, to find all our pages.",
"404_title": "Oops ... There's nothing here ..",
"404_text": "There is nothing to be found here. At the top of the page, you can however find contents in the navigation."
}
}

10
mdorg/hu/footer.json Normal file
View File

@ -0,0 +1,10 @@
{
"tlFooter": {
"contact": "Contact",
"impressum": "Impressum",
"privacy": "Privacy Policy",
"search": "Search",
"search_in_mdorg": "Search museum-digital.org",
"search_in_md": "Search for objects"
}
}

14
mdorg/hu/home.json Normal file
View File

@ -0,0 +1,14 @@
{
"tlHome": {
"pageTitle": "museum-digital",
"pageDescription": "museum-digital is a community project for the digitization of museum and museum object information.",
"pageKeywords": "museums, digitization, community, research",
"opener_title": "Enabling Museums to Let the World in - the Way they Want",
"opener_text": "Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.",
"community_title": "A Community of Like-Minded People",
"community_text": "Lorem adsfjhfsadjhfiosadjfioksdajifojahsdokf jsoa Lorem adsfjhfsadjhfiosadjfioksdajifojahsdokf jsoa Lorem adsfjhfsadjhfiosadjfioksdajifojahsdokf jsoa Lorem adsfjhfsadjhfiosadjfioksdajifojahsdokf jsoa Lorem adsfjhfsadjhfiosadjfioksdajifojahsdokf jsoa Lorem adsfjhfsadjhfiosadjfioksdajifojahsdokf jsoa Lorem adsfjhfsadjhfiosadjfioksdajifojahsdokf jsoa Lorem adsfjhfsadjhfiosadjfioksdajifojahsdokf jsoa Lorem adsfjhfsadjhfiosadjfioksdajifojahsdokf jsoa Lorem adsfjhfsadjhfiosadjfioksdajifojahsdokf jsoa Lorem adsfjhfsadjhfiosadjfioksdajifojahsdokf jsoa Lorem adsfjhfsadjhfiosadjfioksdajifojahsdokf jsoa Lorem adsfjhfsadjhfiosadjfioksdajifojahsdokf jsoa Lorem adsfjhfsadjhfiosadjfioksdajifojahsdokf jsoa Lorem adsfjhfsadjhfiosadjfioksdajifojahsdokf jsoa Lorem adsfjhfsadjhfiosadjfioksdajifojahsdokf jsoa Lorem adsfjhfsadjhfiosadjfioksdajifojahsdokf jsoa Lorem adsfjhfsadjhfiosadjfioksdajifojahsdokf jsoa Lorem adsfjhfsadjhfiosadjfioksdajifojahsdokf jsoa Lorem adsfjhfsadjhfiosadjfioksdajifojahsdokf jsoa Lorem adsfjhfsadjhfiosadjfioksdajifojahsdokf jsoa Lorem adsfjhfsadjhfiosadjfioksdajifojahsdokf jsoa Lorem adsfjhfsadjhfiosadjfioksdajifojahsdokf jsoa ",
"counter_text_museums": "Vom Ausgangspunkt in Sachsen-Anhalt aus wuchs und w\u00e4chst die Zahl der an museum-digital beteiligten Museen zun\u00e4chst naturgem\u00e4\u00df in Deutschland, dann vor allem in Ungarn und dann dar\u00fcber hinaus. Museum-digital versucht ohne hohe Kosten f\u00fcr \u00dcbersetzer m\u00f6glichst viele Sprachgrenzen zu \u00fcberwinden und eine internationale Community entstehen zu lassen.",
"counter_text_collections": "Egal in welcher Region der Erde: Museen fassen Objekte zu Sammlungen zusammen. Die Sammlungen sind dabei oft nach gleichen Gesichtspunkten gegliedert, ein ungarisches Museum kann ebenso eine historische Glassammlung haben wie ein deutsches Museum. F\u00fcr Forscher und andere Interessierte f\u00fchrt museum-digital an dieser Stelle Sammlungen mit gleichem Schwerpunkt zusammen.",
"counter_text_objects": "Als Grenzen, ob politisch, wirtschaftlich oder Sprachgrenzen haben sich im Laufe der Zeit verschoben, Kunst- und Kulturschaffende sind ein- und ausgewandert. Lange bevor die global vernetzte \u00d6konomie f\u00fcr eine internationale Verteilung von Gebrauchs- und Kunstgegenst\u00e4nden sorgte gab es einen regen Austausch und Handel. Im Ergebnis finden sich Objekte zur Geschichte einer Region dieser Erde auch in Museen ganz anderer Regionen. Museum-digital versucht einen zentralen Zugang zu solchen Objekten zu schaffen"
}
}

7
mdorg/hu/impressum.json Normal file
View File

@ -0,0 +1,7 @@
{
"tlImpressum": {
"pageTitle": "Impressum",
"pageDescription": "Impressum of museum-digital.org",
"pageKeywords": "Impressum, museum-digital, museum-digital.org"
}
}

1
mdorg/hu/join_us.json Normal file
View File

@ -0,0 +1 @@
[]

9
mdorg/hu/mission.json Normal file
View File

@ -0,0 +1,9 @@
{
"tlMission": {
"pageTitle": "museum-digital :: Mission and Vision",
"pageDescription": "museum-digital is a project for the digitization of museum data. Here we declare our mission.",
"pageKeywords": "museum-digital, museums, digitization, mission statement, aims",
"missions_title": "Mission",
"missions_introduction": "Museums and their objects should be online! museum-digital's aim is to create simple to use tools and an appropriate environment for this. Museums that use a different software for inventorization can use museum-digital for publishing their data. For all other museums that may not yet have a dedicated inventorization tool museum-digital offers appropriate tools.<\/p>\r\n\r\n<p>museum-digital is a community: all participating museums can join the conversation on what the project should focus on, and how the software is to be developed further. By and by, infrastructure is set up to facilitate and develop the conversation about the digital and museums.<\/p>\r\n\r\n<p>An important principle of museum-digital is to respect existing structures."
}
}

32
mdorg/hu/navigation.json Normal file
View File

@ -0,0 +1,32 @@
{
"tlNavigation": {
"logo_alt_attribute": "Logo of museum-digital",
"news": "News",
"about": "About",
"resources": "Resources",
"software": "Software",
"software_md_ausgabe": "Frontend \/ Portal",
"software_musdb": "musdb",
"software_themator": "Themator",
"software_term_nodac": "md:term & nodac",
"portals": "Portals",
"terminology_work": "Terminological work",
"dashboard": "Dashboard",
"participate": "Participate",
"mission": "Mission",
"resources_links": "Links",
"resources_documents": "Documents",
"third_party": "Third Party Tools",
"publications": "Publications",
"api_based": "Third Party Tools",
"impressum": "Impressum",
"contact": "Contact",
"privacy": "Privacy",
"people": "People",
"calendar": "Calendar",
"development_log": "Development Log",
"faq": "Frequently Asked Questions",
"presentations": "Presentations",
"document_archive": "Document archive"
}
}

16
mdorg/hu/participate.json Normal file
View File

@ -0,0 +1,16 @@
{
"tlParticipate": {
"pageTitle": "museum-digital :: Becoming a Part of museum-digital!",
"pageDescription": "museum-digital is a community project. Of course, we always welcome volunteers, who're ready to help out!",
"pageKeywords": "participation, community, peers, volunteering",
"participate_title": "Becoming a Part of museum-digital",
"participate_introduction": "Helping museum-digital is possible in a multitude of ways. Direct participation is mainly reserved for museums, but anybody can help greatly by providing meaningful information and comments.",
"individuals": "... as an Individual",
"individuals_title": "... as an Individual",
"individuals_text": "You can help museums greatly by providing information and working with the museums. At the bottom of almost all object pages, there is a link \"Do you know more ...?\". By clicking on this line, you can directly provide e-mail feedback on the given object to the museum concerned. You may however also offer helping out the museum in your area of expertise.",
"local_museum_title": "Helping Out at Your Local Museum",
"local_museum_text": "Many, if not most, museums welcome little more than a helping hand. ",
"institutions_title": "... as an Institution",
"institutions_text": "If your institution wants to join museum-digital, you only need a short description, a photo, and the usual contact information of the museum. The museum will then be entered into the appropriate instance of museum-digital and a user account for the museum will be set up. Our tools have shown to be sufficiently intuitive for half an hour of an introduction (via phone) to be sufficient for publishing an object.<\/p>\r\n\r\n<p>Regional museum associations often offer day-long seminars in which working with museum-digital is discussed in more detail. These events usually feature hands-on exercises. It may be fruitful to consult your regional museum association or the administrator of your regional instance of museum-digital."
}
}

18
mdorg/hu/people.json Normal file
View File

@ -0,0 +1,18 @@
{
"tlPeople": {
"pageDescription": "Profile page of %s at museum-digital",
"on": "On",
"tel": "Tel.",
"email": "e-Mail",
"html_feed": "HTML feed",
"rss": "RSS",
"md_blog": "museum-digital blog",
"affiliation": "Affiliation",
"blog_posts_by": "Blog Posts by %s",
"overviewTitle": "Team :: museum-digital",
"overviewDescription": "museum-digital is people. Here you can some people from our core team.",
"overviewKeywords": "museum-digital, team, people",
"overviewListTitle": "Team",
"overviewListSummary": "museum-digital is - in effect - people. Here you can find a list of some of our core team members in random order."
}
}

31
mdorg/hu/portals.json Normal file
View File

@ -0,0 +1,31 @@
{
"tlPortals": {
"pageTitle": "museum-digital :: Portals",
"pageDescription": "museum-digital is represented on different, regional portals. Here, there is a list of them.",
"pageKeywords": "museum-digital, portals, museum objects, access",
"portals_title": "The Different Portals of museum-digital",
"portals_introduction": "museum-digital is composed of different portals. Most of them are regionally structured.",
"international_portals": "International Portals",
"german_portals": "Regional portals in Germany",
"themator_title": "Themator: Topical Portals",
"themator_introduction": "The themator is a tool we developed to enable museums and like-minded people to create digital exhibitions and - more generally - to easily engage in digital storytelling. As the themator is largely monolingual, we have set up different instances of it.",
"md_term_title": "md:term: The Controlled Vocabularies of museum-digital Made Accessible",
"md_term_introduction": "About 2010, we started to use controlled vocabularies to facilitate the common tagging and interlinking of digitized objects. For a long time, these vocabularies were not accessible for any outside viewers. Since they may be a useful resource to some, we since developed md:term as a public and hopefully easily accessible portal for our (and some other) controlled vocabularies.",
"Germany": "Germany",
"Hungary": "Hungary",
"Brazil": "Brazil",
"Indonesia": "Indonesia",
"themator_in_german": "Themator in German",
"themator_in_hungarian": "Themator in Hungarian",
"Austria": "Austria",
"hungarian_portals": "Hungarian Regional Portals",
"portals_in_serbia": "Regional Portals in Serbia",
"portals_in_romania": "Regional Portals in Romania",
"portals_in_the_usa": "Regional Portals in the USA",
"Worldwide": "Worldwide",
"about_resources": "Resources",
"Switzerland": "Switzerland",
"portals_in_switzerland": "Regional portals in Switzerland",
"portals_in_austria": "Regional portals in Austria"
}
}

9
mdorg/hu/privacy.json Normal file
View File

@ -0,0 +1,9 @@
{
"tlPrivacy": {
"pageTitle": "museum-digital :: Privacy Policy",
"pageDescription": "Privacy policy of museum-digital.org",
"pageKeywords": "privacy policy, privacy",
"title": "Privacy Policy",
"text_content": "This is the privacy policy of "
}
}

10
mdorg/hu/resources.json Normal file
View File

@ -0,0 +1,10 @@
{
"tlResources": {
"pageTitle": "museum-digital :: Resources",
"pageDescription": "Here you can find resources on museum-digital specifically and those relevant to the digitization in museums in general.",
"pageKeywords": "museums, resources, materials",
"resources_title": "Resources",
"resources_introduction": "Relevant resources can be found here.",
"general": "General"
}
}

9
mdorg/hu/resources_documents.json Normal file
View File

@ -0,0 +1,9 @@
{
"tlDocuments": {
"pageTitle": "museum-digital :: Resources",
"pageDescription": "A selection of helpful documents for about museum work in general and digital museum work in specific can be found here.",
"pageKeywords": "documents, museums, museums work, digitization, inventorization",
"title": "Documents",
"introduction": "A selection of helpful documents for about museum work in general and digital museum work in specific can be found here."
}
}

14
mdorg/hu/resources_links.json Normal file
View File

@ -0,0 +1,14 @@
{
"tlLinks": {
"pageTitle": "museum-digital :: Links",
"pageDescription": "A selection of relevant links about museum digitization can be found here.",
"pageKeywords": "Links, museums, digitization in museums, museum portals",
"title": "Links",
"introduction": "Here you can find a list of interesting links.",
"museum_portals": "Other Museum (Object) Portals",
"organizations": "Organizations",
"name": "Name",
"country": "Country",
"description": "Description"
}
}

16
mdorg/hu/software.json Normal file
View File

@ -0,0 +1,16 @@
{
"tlSoftware": {
"pageTitle": "museum-digital :: Software",
"pageDescription": "At museum-digital, we have developed a set of software solutions to aid different parts of museum (digitization) work.",
"pageKeywords": "software, museums, museum objects, museum software, museum-digital",
"software_title": "Software",
"software_introduction": "At museum-digital, we have developed a set of software solutions to facilitate an easy and inclusive process of digitizations in museums. Originally, museum-digital was founded to publish object information online. We thus began by developing a <a href=\"\/software\/frontend\">public interface for viewing object information<\/a>.\r\n<\/p>\r\n<p>\r\nSince the original method of data input - the museums entered their data into their local database, sent it to the programmers, the programmers entered it to museum-digital - did not scale well, we then developed a simple online input interface, <a href=\"\/software\/musdb\">musdb<\/a>. Some museums, that did not yet have a dedicated database for inventorization data, but knew musdb well, began to ask additional inventorization functionalities. And thus the approach of musdb changes: instead of being an input interface to a publication platform, it turned into an inventorization tool with the option to publish.\r\n<\/p>\r\n<p>\r\nSoon after, requests for options to more thoroughly present digital narratives and stories became more frequent. While museum objects may be interesting by themselves, it is also a central task of museums to contextualize them. As a reaction to these requests, we created the <a href=\"\/software\/themator\">Themator<\/a> as an independent tool for writing and publishing stories online.\r\n<\/p>\r\n<p>\r\nEarly on, when developing the main frontend and musdb, we decided to use controlled vocabularies for all databases of a given language. Internally, we use our \"norm data control tool\" <a href=\"\/software\/term_nodac\">nodac<\/a> for curating these. Since the vocabularies have grown considerably since, and have become a useful resource on their own by now, we have also developed a searchable frontend for these, <a href=\"\/software\/term_nodac\">md:term<\/a>.",
"frontend_portal": "Frontend \/ Portals",
"musdb": "musdb",
"themator": "Themator",
"term_nodac": "md:term & nodac",
"resources": "Resources",
"in_blog": "Tech-Related News in our Blog",
"third_party_tools": "Third party tools"
}
}

9
mdorg/hu/software_development_log.json Normal file
View File

@ -0,0 +1,9 @@
{
"tlDevLog": {
"pageTitle": "Development Log :: museum-digital",
"pageDescription": "Log of development on museum-digital",
"pageKeywords": "Software, museum-digital, Development",
"status": "Status",
"development_log": "Development Log"
}
}

44
mdorg/hu/software_frontend.json Normal file
View File

@ -0,0 +1,44 @@
{
"tlFrontend": {
"pageTitle": "museum-digital :: The Main Frontend \/ Portal Software",
"pageDescription": "Most of the work museum-digital does focuses on bringing museums online. We do so mainly using our main frontend \/ portal software.",
"pageKeywords": "software, museums, museum objects, museum software, exhibitions, web portal",
"frontend_title": "The Main Frontend of museum-digital",
"frontend_introduction": "museum-digital was founded to publish museum object information online. That's not possible without the right software.<\/p>\r\n<p>The \"frontend\" is thus the first application, that at museum.digital. With it, museums can join together to present themselves and their objects online.<\/p>\r\n<p>To offer a comprehensive glimpse at the museums and their objects, a variety of additional information has been made presentable since. On the one hand, museums can now add information on their collections, object groups, exhibitions, and events. On the other, a number of options for linking and visualizing information have been added.",
"technical_title": "Technical Information",
"design_principles_title": "Focus - Design Principles",
"design_principles_text": "\"The \"frontend\" of museum-digital is primarily designed to always offer a clear focus on whichever information is central to a given page or section. This provides for an easy of understanding. A lot of additional options exist for power users - from visualizations to a command line menu embedded into the website. These are however \"hidden\" in sidebars or only accessible through keyboard shortcuts, so that they don't irritate first-time users.",
"api_title": "API(s)",
"api_text": "Publishing and making things accessible doesn't only mean making it possible to view something. It also means enabling people to use data to realize their own ideas. Accordingly, all information that is published using the \"frontend\" of museum-digital is also accessible in a machine-readable way via our <abbr title=\"JavaScript Object Notation\">JSON<\/abbr> API.<\/p><p>As much as possible, the \"frontend\" provides information in open standards as well: object information can be accessed in <a href=\"http:\/\/network.icom.museum\/cidoc\/working-groups\/lido\/what-is-lido\/\">LIDO<\/a>, information about museums can be downloaded as electronic business cards (<a href=\"https:\/\/de.wikipedia.org\/wiki\/VCard\">vCard<\/a>), and calendar information such as exhibitions can be integrated with calendar tools using the <a href=\"https:\/\/de.wikipedia.org\/wiki\/ICalendar\">iCalendar<\/a> standard.",
"development_title": "Development",
"development_text": "The \"frontend\" of museum-digital is built using PHP8 and MySQL. JavaScript is used for interactive features and visualizations. A list of the used libraries can be found <a href=\"https:\/\/handbook.museum-digital.info\/?lan=de&q=Weiteres\/Dependencies\">here<\/a>. We use <a href=\"https:\/\/git-scm.com\/\">git<\/a> for version control.",
"screenshots": "Screenshots",
"resources": "Resources",
"in_blog": "News About the Frontend in the Blog",
"screenshot-startpage": "Start page of the German national portal of museum-digital.",
"extended_search_alt": "Extended search page in the museum-digital frontend.",
"screenshot_extended_search": "Using the extended search settings, users can define exact searches.",
"screenshot_enriched_search_results_alt": "Enriched search results in the museum-digital frontend",
"screenshot_enriched_search_results": "Search result pages are enriched based on data from our <a href='\/about\/terminology'>controlled vocabularies<\/a>.",
"in_handbook": "Handbook pages about the frontend",
"api_link": "Short introduction to the API",
"screenshot_timeline_alt": "A timeline page in museum-digital.",
"screenshot_timeline": "The museum-digital frontend offers a timeline, for viewing search results sorted by their relations to time.",
"screenshot_oak_alt": "Objects on map pages in museum-digital.",
"screenshot_oak": "Using the \"objects on map\" pages, users can find interesting objects based on their geographical background.",
"screenshot_object_page_alt": "An object page.",
"screenshot_object_page": "An object page in the frontend of museum-digital.",
"screenshot_multilinguality_alt": "Multilinguality in the museum-digital frontend.",
"screenshot_multilinguality": "museum-digital is multilingual, and so can be the displayed entries. The navigation language and the record language can be switched independent of each other.",
"screenshot_exhibition_tiles_alt": "Exhibition overview page in the museum-digital frontend",
"screenshot_exhibition_tiles": "The exhibition overview page in tiles mode.",
"screenshot_calendar_alt": "Calendars are available for exhibitions and events.",
"screenshot_calendar": "Calendars are available for exhibitions and events.",
"screenshot_graph_view_alt": "\"Graph view\"",
"screenshot_graph_view": "The \"graph view\" offers users an alternative option for navigating the portal.",
"screenshot_command_line_alt": "Keyboard control of the museum-digital frontend.",
"screenshot_command_line": "Power users can navigate the portal using their keyboard through an emacs-inspired interface.",
"screenshot_compare_objects_alt": "Comparing obects",
"screenshot_compare_objects": "Two objects can be compared with each other"
}
}

45
mdorg/hu/software_musdb.json Normal file
View File

@ -0,0 +1,45 @@
{
"tlMusdb": {
"pageTitle": "museum-digital :: musdb",
"pageDescription": "musdb is museum-digital's tool for indexing and inventorization. It has in many ways developed into a more general museum-management tool.",
"pageKeywords": "musdb, museum-management, inventorization, software",
"musdb_title": "musdb",
"musdb_introduction": "musdb is museum-digital's tool for indexing and inventorization. Originally developed for recording objects to be published only, it has since developed into a full-featured inventorization and museum management solution.<\/p>\r\n<p>Central to the development of musdb are:<\/p>\r\n<ul>\r\n<li>musdb is developed based on requests by and communications with the museums using it<\/li>\r\n<li>musdb is being with collaboration in mind: New features and fixes are available to all museums<\/li>\r\n<li>using musdb means working collaboratively: the controlled vocabularies, that are used for linking people, times, places, and tags, are used together by all museums of a given language<\/li>\r\n<li>working with musdb should be as easy and intuitive as possible<\/li>\r\n<li>Tips and warnings are given to not just enter data, but to create high quality data<\/li>\r\n<\/ul>",
"technical_title": "Technical Information",
"design_principles_title": "Design Principles",
"design_principles_text": "musdb should be easy and intuitive to use. It should be fun to use. One the one hand, this means that the design should give a clear focus to the main subject of a given page. To reach this aim, options exist to toggle many features on or off. Optional features (like generating QR codes for object pages or a table of contents to directly jump to the wanted section of a page) are available in a toolbox on the left border of the window.<\/p>\r\n\r\n<p>But easy and intuitive also means that power users can work efficiently in whatever way suits them best. musdb offers a variety of helpers for this. A selection of these are:<\/p>\r\n\r\n<ul>\r\n<li>Clicking into a field, users can see how many characters have been entered, how many are required, and how many are allowed at max.<\/li>\r\n<li>PuQi: the \"Publication Quality Index\" shows, how object information can be enhanced<\/li>\r\n<li>Plausi: using the controlled vocabularies, musdb can warn about implausible entries (e.g. a painter cannot have painted a painting before she was born)<\/li>\r\n<li>Text blocks provide for a quick entry of similar contents<\/li>\r\n<\/ul>",
"development_title": "Development",
"development_text": "musdb is based on PHP8 and MySQL. A number of PHP and JavaScript libraries are used, a list of which can be found <a href=\"https:\/\/handbook.museum-digital.info\/?lan=de&q=Weiteres\/Dependencies#2\">in the handbook<\/a>.",
"screenshots": "Screenshots",
"resources": "Resources",
"in_handbook": "Documentation for musdb",
"videos_and_screencasts": "Videos and Screencasts on YouTube",
"in_blog": "News About the Development of musdb",
"screenshot_dashboard_alt": "Dashboard \/ default startpage of musdb.",
"screenshot_dashboard": "The default start page is a customizable dashboard. Other start pages can be selected by the user.",
"screenshot_batch_editing_alt": "Batch editing in musdb.",
"screenshot_batch_editing": "musdb features batch editing functionalities for e.g. batch publishing or tagging.",
"screenshot_xml_export_alt": "XML export",
"screenshot_xml_export": "Users can export their data in our own md:xml (a simple notation featuring all available fields) and <a href='http:\/\/lido-schema.org'>LIDO<\/a>.",
"screenshot_backgrounds_alt": "Background research tool.",
"screenshot_backgrounds": "Using the \"backgrounds\" section, users can browse the controlled vocabularies directly from musdb.",
"screenshot_find_an_export_alt": "Find an expert: Connecting users.",
"screenshot_find_an_export": "Using the \"Find an Export\" button, users can find other users who have done much work on a given topic. Still, every user can decide if they want to let others find them through this tool or not.",
"screenshot_multilingual_alt": "Multilingual usage of musdb.",
"screenshot_multilingual": "musdb is multilingual and it can handle multilingual inputs.",
"screenshot_navigation_alt": "Navigation of musdb.",
"screenshot_navigation": "The navigation gives a rough overview over different sections of musdb: museums, collections, objects, object groups, exhibitions, etc.",
"screenshot_object_overview_alt": "Object overview page.",
"screenshot_object_overview": "An object overview page in image mode. The sidebar on the right offers search and filter-based exporting and batch editing functionalities. A simple list view is also available.",
"screenshot_object_page_alt": "Object page.",
"screenshot_object_page": "The main section of an object page. At the top, most basic information on the object can be entered. At the bottom, the tabbed menu for managing detailed information on the object can be seen.",
"screenshot_record_history_alt": "Record history of an object.",
"screenshot_record_history": "Edits to an object are logged. If the user who previously edited the object set up their user profile, new users who see the logs can get to know others from the museum through the logs.",
"screenshot_provenance_research_alt": "Provenance research tab.",
"screenshot_provenance_research": "Using the provenance research tab, detailed reports on a predefined set of critical issues can be recorded.",
"screenshot_restoration_alt": "Restoration tab on a musdb object page.",
"screenshot_restoration": "The restoration tab of an object page offers options for color-coded and easily accessible notes towards the top of the section, detailed ones on the bottom.",
"screenshot_user_management_alt": "User management and user rights section.",
"screenshot_user_management": "Museum directors and regional administrators set detailed permissions for what users can edit or view."
}
}

9
mdorg/hu/software_term_nodac.json Normal file
View File

@ -0,0 +1,9 @@
{
"tlTermNodac": {
"pageTitle": "museum-digital :: Nodac & md:term",
"pageDescription": "At museum-digital we build two tools for managing and displaying controlled vocabularies: md:term and nodac.",
"pageKeywords": "software, controlled vocabularies, subject headings",
"term_nodac_title": "Our Tools for Managing Controlled Vocabularies: nodac and md:term",
"term_nodac_introduction": "nodac is the name of our tool for correcting, enriching, and hierarchializing controlled vocabularies at museum-digital. Nodac is multilingual and can be used for controlling vocabularies in different languages. Using nodac, external vocabularies can be managed as well: for example the Hornbostel-Sachs-Systematik for Musikinstrumente or the Hessische Systematik. The primary use of the tool remains, however, the curation of the museum-digital's own controlled vocabularies. It is the dedicated place for in-depth enrichment of terms from the domains of \"actors\" (people and institutions), geographic places, times, and tags. These are controlled centrally for a given language by the <i>norm data editors<\/i>. Each participating museum can however submit requests for changes.<\/p>\r\n\r\n<p>While it is the dedicated aim of museum-digital to make entering and linking - for example - a tag as easy as possible for the museums, further edits like providing a definition of the term and linking it with other controlled vocabularies are taken over by the <i>norm data editors<\/i>. It thus becomes a background task, that does however remain central to the success of the whole endeavor. It is only because we keep curated controlled vocabularies, that we can generate correct timelines or place objects on maps in any meaningful way.<\/p>\r\n\r\n<p>md:term is the public equivalent of nodac. It provides for public, structured access to our own vocabularies and a number of external ones. Besides making the vocabularies browse-able, it offers <a href=\"https:\/\/en.wikipedia.org\/wiki\/Simple_Knowledge_Organization_System\"><abbr title=\"Simple Knowledge Organization System\">SKOS<\/abbr><\/a> and <abbr title=\"JavaScript Object Notation\">JSON<\/abbr> interfaces. In this way, it provides access for other developers and projects to creatively use and incorporate our controlled vocabularies."
}
}

15
mdorg/hu/software_themator.json Normal file
View File

@ -0,0 +1,15 @@
{
"tlThemator": {
"pageTitle": "museum-digital :: Themator",
"pageDescription": "The Themator is museum-digital's solution for digital story-telling.",
"pageKeywords": "software, story-telling, topics, stories, narrative, exhibitions",
"themator_title": "The Themator - A Tool for Online Storytelling and Digital Exhibitions",
"screenshots": "Screenshots",
"themator_introduction": "The Themator is museum-digital's solution for digital story-telling.<\/p><p>After setting up the <a href=\"\/software\/frontend\">main frontend<\/a> for museum-digital, questions for how to embed the thus published objects in online narratives soon arose. To answer this demand, the development of the Themator began.<\/p><p>The Themator is structured around topics, which can be super- or subordinate to other topics and which can be associated with objects (both those entered only in the Themator and those published in any of the <a href=\"\/about\/portals\">main portals of museum-digital<\/a>), literature entries, and more. This focus on <em>topics<\/em> provides for a broad range of possible uses in the field of digital storytelling, especially where it relates to museum objects. On the one hand, the Themator can be used for creating digital exhibitions. On the other, it has been used to create learning materials (e.g. <a href=\"https:\/\/hu.museum-digital.org\/themator\/ausgabe\/showthema.php?m_tid=1&tid=1&ver=standalone\">for teaching in German minority schools in Hungary<\/a>). This, combined with the need to be able to embed objects from the different instances in the same topic, led us to design the Themator as a tool completely independent from the main instances.",
"screenshot_overview_germany": "Overview of topics available in the German-language Themator",
"screenshot_topic_page": "A topic page in the Themator",
"screenshot_exhibition_view": "The Themator features a slideshow-like \"exhibition view\"",
"screenshot_linked_objects": "List of objects linked to a topic",
"screenshot_object_page": "Page for a single object. Besides those entered only in the Themator, objects can also be embedded from museum-digital"
}
}

14
mdorg/hu/software_third_party.json Normal file
View File

@ -0,0 +1,14 @@
{
"tlThirdParty": {
"pageTitle": "museum-digital :: Third Party Tools",
"pageDescription": "Based on the APIs of museum-digital, a number of third party tools have been written. Here you can find some of them.",
"pageKeywords": "software, museum software, API, digitization in museums",
"title": "Third Party Tools",
"introduction": "Using the different APIs of museum-digital, a number of additional tools have been written. These are in principle independent of museum-digital, but since they interact with or are based on museum-digital in some way, we collect brief introductions to those we know of here.",
"resources": "Resources",
"in_blog": "News About API-Based Tools in our Blog",
"website": "Website",
"license_usage": "License \/ Usage",
"authors": "Author(s)"
}
}

12
mdorg/hu/statistics.json Normal file
View File

@ -0,0 +1,12 @@
{
"tlStatistics": {
"frontend": "Frontend",
"musdb": "musdb",
"themator": "Themator",
"noda": "md:term \/ nodac",
"others": "Others",
"Total": "Total",
"Checked": "Checked",
"users": "Users"
}
}

11
mdorg/hu/terminology.json Normal file
View File

@ -0,0 +1,11 @@
{
"tlTerminology": {
"pageTitle": "museum-digital :: Terminological Work at museum-digital",
"pageDescription": "At museum-digital we use controlled vocabularies, to enrich the users' experience. Here we describe, how they are handled.",
"pageKeywords": "Terminology, museums, controlled vocabularies, tagging",
"terminology_title": "Controlled Vocabularies at museum-digital",
"terminology_role_of_terminology": "Controlled vocabularies are a central issue to museum-digital. Sorted into four catalogs (persons and institutions, geographical places, times, and tags), terms are enriched with definitions and links to external controlled vocabularies and services (Wikipedia, GND, ULAN, RKD, MBL, LAGIS, geonames, TGN, AAT, LCSH, ...). At the same time, they are categorized hierarchically. This provides for the possibility to return objects linked to subordinate terms to searches for a given superordinate term. A search for \"vehicle\" thus returns any object linked to \"car\" as well.",
"terminology_how_we_do_it": "How are the Vocabularies Controlled?",
"terminology_how_we_do_it_text": "<p>The curation of controlled vocabularies at museum-digital takes place in a centralized manner. All museums of all instances of a given primary language work together to create a common database of controlled terms. Since curating controlled vocabularies is time consuming, we try to reduce the participating museums' workload in this regard as much as possible. Besides, a centralized curation of controlled vocabularies leads to more uniform results.<\/p><p>To ease the curation, we have developed a tool, <a href=\"\/software\/term_nodac\">\"nodac\"<\/a>, which automatizes much of the enrichment work and offers a simple interface for positioning terms hierarchically. With this tool, norm data editors, can also use batch editing functionalities for enhancing the controlled vocabularies.<\/p><p>The curation of controlled vocabularies is thus a joint effort of the participating museums, direct volunteering, and support by a number of state governments, led by a small team of \"norm data editors\".<\/p>"
}
}