- Can started to work on the Turkish translation.
- Carrey continued proofreading the English translation. - Mariam continued translating to Arabic.
This commit is contained in:
jrenslin authored and 
Stefan Rohde-Enslin committed
1 parent
f59fab614d
commit
9d4149122b
42 files changed
+308
-303
No files matched your search
@@ -5,6 +5,7 @@
|
||||
"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."
|
||||
"calendar_introduction": "On this page you can find current events concerning museum-digital, e.g. seminars.",
|
||||
"attendees": "Attendees"
|
||||
}
|
||||
}
|
||||
@@ -2,8 +2,8 @@
|
||||
"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",
|
||||
"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."
|
||||
"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."
|
||||
}
|
||||
}
|
||||
@@ -5,12 +5,12 @@
|
||||
"about": "About",
|
||||
"resources": "Resources",
|
||||
"software": "Software",
|
||||
"software_md_ausgabe": "Frontend \/ Portal",
|
||||
"software_md_ausgabe": "Frontend\/Portal",
|
||||
"software_musdb": "musdb",
|
||||
"software_themator": "Themator",
|
||||
"software_term_nodac": "md:term & nodac",
|
||||
"portals": "Portals",
|
||||
"terminology_work": "Terminological work",
|
||||
"terminology_work": "Terminology work",
|
||||
"dashboard": "Dashboard",
|
||||
"participate": "Participate",
|
||||
"mission": "Mission",
|
||||
@@ -19,7 +19,7 @@
|
||||
"third_party": "Third Party Tools",
|
||||
"publications": "Publications",
|
||||
"api_based": "Third Party Tools",
|
||||
"impressum": "Impressum",
|
||||
"impressum": "Copyright",
|
||||
"contact": "Contact",
|
||||
"privacy": "Privacy",
|
||||
"people": "People",
|
||||
|
||||
@@ -1,16 +1,16 @@
|
||||
{
|
||||
"tlParticipate": {
|
||||
"pageTitle": "Becoming a Part of museum-digital! :: 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",
|
||||
"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": "... 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.",
|
||||
"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 regional instance of museum-digital."
|
||||
"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."
|
||||
}
|
||||
}
|
||||
@@ -10,9 +10,9 @@
|
||||
"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",
|
||||
"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."
|
||||
"overviewListSummary": "Museum-digital is - in effect - people. Here you can find a list of some of our core team members in random order."
|
||||
}
|
||||
}
|
||||
@@ -1,16 +1,16 @@
|
||||
{
|
||||
"tlPortals": {
|
||||
"pageTitle": "Portals :: museum-digital",
|
||||
"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.",
|
||||
"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": "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.",
|
||||
"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",
|
||||
|
||||
@@ -1,9 +1,9 @@
|
||||
{
|
||||
"tlPrivacy": {
|
||||
"pageTitle": "Privacy Policy :: museum-digital",
|
||||
"pageDescription": "Privacy policy of museum-digital.org",
|
||||
"pageKeywords": "privacy policy, privacy",
|
||||
"pageDescription": "Privacy Policy of museum-digital.org",
|
||||
"pageKeywords": "privacy Policy, Privacy",
|
||||
"title": "Privacy Policy",
|
||||
"text_content": " <h3>Erkl\u00e4rung zum Schutz personenbezogener Daten<\/h3>\r\n\r\n <p>Gem\u00e4\u00df der Datenschutzgrundverordnung sind wir verpflichtet den Webseitenbesucher zu Beginn\r\n des Nutzungsvorgangs \u00fcber Art, Umfang und Zweck der Erhebung und Verwendung personenbezogener Daten zu unterrichten. In dieser Datenschutzerkl\u00e4rung erfahren Sie, welche Daten von uns erfasst werden, zu welchen Zwecken wir die Daten erfassen und was mit den erfassten Daten passiert. Da dies wichtig ist, sollten Sie sich die Zeit nehmen, diese Datenschutzerkl\u00e4rung sorgf\u00e4ltig zu lesen.<\/p>\r\n\r\n <h3>Zweck der Erhebung, Verarbeitung oder Nutzung Ihrer Daten<\/h3>\r\n <p>\r\n Ihre Daten ben\u00f6tigen wir:\r\n <ol>\r\n <li>Zur Optimierung unseres Angebots.<\/li>\r\n <\/ol>\r\n Wir erheben Ihre Daten nur soweit dies notwendig ist. Ihre übersandten Daten werden nicht an Markt- oder Meinungsforschung weiter gegeben.\r\n <\/p>\r\n\r\n <h3>Datennutzung und Freiwilligkeit der Einwilligung<\/strong><\/h3>\r\n <p>\r\n Alle personenbezogenen Daten, die von Ihnen an uns \u00fcbermittelt wurden, werden nur f\u00fcr den Zweck verwendet,\r\n f\u00fcr die Sie uns die Daten zur Verf\u00fcgung gestellt haben. Entf\u00e4llt dieser Zweck so werden die Daten gel\u00f6scht. Sie k\u00f6nnen unsere Webseite besuchen, ohne dass wir pers\u00f6nliche Daten erheben. \r\n Ihre pers\u00f6nlichen Daten ben\u00f6tigen wir allerdings dann wenn Sie mit uns in Kontakt treten m\u00f6chten \r\n z.B. durch eine Anfrage. Dies begr\u00fcndet dann auch die Rechtsgrundlage zur Datennutzung damit wir unseren\r\n Rechten und Pflichten aus der Gesch\u00e4ftsverbindung mit Ihnen nachkommen k\u00f6nnen, gem\u00e4\u00df § 28 Abs.1 BDSG.\r\n <\/p>\r\n\r\n\r\n <p>\r\n Ihre personenbezogenen Daten welche uns über unsere Webseite übersandt \r\n werden erheben, verarbeiten oder nutzen wir nur im \r\n Rahmen der gesetzlichen Bestimmungen. Ihre Einwilligung erfolgt auf freier Entscheidung und ohne Zwang und ist jederzeit widerrufbar.\r\n <\/p>\r\n\r\n \r\n <h3>Erfassung von allgemeinen Daten und Informationen<\/h3>\r\n\r\n<p>Der Server von museum-digital erfasst bei jedem Aufruf eine Reihe von allgemeinen Daten und Informationen in den Logfiles. Erfasst werden \r\n<ol>\r\n <li>der vom Aufrufenden verwendeten Browser,<\/li>\r\n <li>das vom Aufrufenden verwendete Betriebssystem,<\/li>\r\n <li>die Internetseite, von welcher der Aufrufende auf unsere Webseite gelangt ist,<\/li>\r\n <li>die Unterwebseiten, welche vom Aufrufenden auf unserer Webseite angew\u00e4hlt werden,<\/li>\r\n <li>das Datum und die Uhrzeit eines Zugriffs,<\/li>\r\n <li>eine Internet-Protokoll-Adresse (IP-Adresse),<\/li>\r\n <li>der Internet-Service-Provider des Aufrufenden und<\/li>\r\n <li>sonstige \u00e4hnliche Daten und Informationen, die der Gefahrenabwehr im Falle von Angriffen auf museum-digital.de dienen.<\/li>\r\n<\/ol>\r\n\r\nBei der Nutzung dieser allgemeinen Daten und Informationen zieht museum-digital keine R\u00fcckschl\u00fcsse auf die betroffene Person. Diese anonym erhobenen Daten und Informationen werden durch museum-digital statistisch ausgewertet. Die anonymen Daten der Server-Logfiles werden getrennt von allen eventuell durch eine betroffene Person angegebenen personenbezogenen Daten gespeichert.<\/p>\r\n\r\n \r\n \r\n \r\n <h3>Einsatz von Cookies<\/h3>\r\n <p>Um unseren Internetauftritt f\u00fcr Sie benutzerfreundlich zu gestalten und optimal auf Ihre Bed\u00fcrfnisse abzustimmen, setzen wir in einigen\r\n Bereichen Cookies ein. Ein Cookie ist eine kleine Datei, die lokal auf Ihrem Computer gespeichert wird, sobald Sie eine Website besuchen.\r\n Ihr Browser bietet eine Funktion an, Cookies zu l\u00f6schen (z.B. \u00fcber Browserdaten l\u00f6schen). Weitere Informationen dazu finden Sie in\r\n der Bedienungsanleitung bzw. in der Regel unter Einstellungen Ihres Internet-Browsers. Im Einzelnen wird bei jedem Abruf Folgendes gespeichert:\r\n <\/p>\r\n <ul>\r\n <li>Speichern des Opt-Outs aus Matomo (siehe unten)<\/li>\r\n <\/ul>\r\n\r\n <h3>Tracking (Matomo)<\/h3>\r\n <p>\r\n Auf dieser Website werden unter Einsatz der Webanalysedienst-Software Matomo (www.matomo.org), einem Dienst des Anbieters InnoCraft Ltd., 150 Willis St, 6011 Wellington, Neuseeland, (\u201eMataomo\u201c) auf Basis unseres berechtigten Interesses an der statistischen Analyse des Nutzerverhaltens zu Optimierungs- und Marketingzwecken gem\u00e4\u00df Art. 6 Abs. 1 lit. f DSGVO Daten gesammelt und gespeichert. Aus diesen Daten k\u00f6nnen zum selben Zweck pseudonymisierte Nutzungsprofile erstellt und ausgewertet werden. Die mit der Matomo-TechnoloLine truncated
|
||||
"text_content": " <h3>Declaration of the Protection of Personal Data<\/h3>\r\n\r\n <p>In accordance with the General Data Protection Regulation, we are obliged to inform the website visitor at the beginning of their usage of this site about the nature, scope, and purpose of the collection and use of personal data. In this privacy statement you will learn which data we collect, for what purposes we collect the data, and what happens to the data collected. Since this is important, you should take the time to read this privacy policy carefully.<\/p>\r\n\r\n <h3>Purpose of Collecting, Processing, or Using Your Data<\/h3>\r\n <p>\r\n We need your data:\r\n <ol>\r\n <li>1. To optimize our offerings.<\/li>\r\n <\/ol>\r\n We only collect your data when necessary. Your information will not be given to third parties for market or opinion research.\r\n <\/p>\r\n\r\n <h3>Data Usage and Voluntariness of Consent<\/strong><\/h3>\r\n <p>\r\n All personal identifiable information you submit to us will only be used for the purpose for which you consented to provide us with. If this purpose is omitted, the data will be deleted. You can visit our website without us collecting personal information. However, we require your personal data if you would like to contact us, e.g. by a request. This then also establishes the legal basis for the use of data so that we can meet our rights and obligations arising from the business relationship with you, in accordance with \u00a7 28 Abs.1 BDSG.\r\n <\/p>\r\n\r\n\r\n <p>\r\n Your personal data sent to us via our website will be collected, processed or used only in accordance with the statutory provisions. Your consent is made at your own discretion and without compulsion and is revocable at any time.\r\n <\/p>\r\n\r\n \r\n <h3>Collection of General Data and Information<\/h3>\r\n\r\n<p>The server of museum-digital collects a series of general data and information in the logfiles every time it is called up. To be collected:\r\n<ol>\r\n <li>the browser used by the individual,<\/li>\r\n <li>the operating system used by the individual,<\/li>\r\n <li>the website from which the caller came to our website,<\/li>\r\n <li>the sub-web pages, which are selected by the caller on our website,<\/li>\r\n <li>the date and time of visit,<\/li>\r\n <li>an Internet-Protocol Address (IP Address),<\/li>\r\n <li>the internet service provider of the individual and<\/li>\r\n <li>other similar data and information that serve security purposes in case of attacks on museum-digital.de.<\/li>\r\n<\/ol>\r\n\r\nWhen using this general data and information, museum-digital does not draw any conclusions about the person concerned. This anonymously collected data and information are statistically evaluated by museum-digital. The anonymous data of the server log files are stored separately from any personal data that may be provided by an affected person.<\/p>\r\n\r\n \r\n \r\n \r\n <h3>Use of Cookies<\/h3>\r\n <p>In order to make our website user-friendly and to optimally match your needs we use cookies in some areas. A cookie is a small file that is stored locally on your computer as soon as you visit a website. Your browser offers a feature to delete cookies (for example, delete via browser data). Further information can be found in the operating instructions or usually under Settings of your Internet browser. Specifically, the following is stored with each access:\r\n <\/p>\r\n <ul>\r\n <li>Saving the opt-out from Matomo (see below)<\/li>\r\n <\/ul>\r\n\r\n <h3>Tracking (Matomo)<\/h3>\r\n <p>\r\n On this website, using the web analysis service software Matomo (www.matomo.org), a service of the provider InnoCraft Ltd., 150 Willis St, 6011 Wellington, New Zealand, (\"Mataomo\") based on our legitimate interest in the statistical analysis of user behavior for optimization and marketing purposes in accordance with Art. 6 para. 1 lit. f DSGVO data collected and stored. From this data, pseudonymised usage profiles can be created and evaluated for the same purpose. The data collected using Matomo technology (including your anonymous IP address) will be processed on our servers. The information generated in the pseudonymous user profile is not used to personally identify the visitor to this website and is not merged with personal data about the bearer of the pseudonym. If you do not agree with the storage and evaluation of this data from your visit, then you can object to the storage and use at any time by clicking the mouse. In this case, a so-called opt-out cookie is stored in your browser, with the result that Matomo does not collect any session data. Please note that the complete deletion of your cookies means that the opt-out cookie is also deleted and may need to beLine truncated
|
||||
}
|
||||
}
|
||||
@@ -1,8 +1,8 @@
|
||||
{
|
||||
"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",
|
||||
"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"
|
||||
|
||||
@@ -1,9 +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",
|
||||
"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 for about museum work in general and digital museum work in specific can be found here."
|
||||
"introduction": "A selection of helpful documents about museum work in general and specific digital museum work can be found here."
|
||||
}
|
||||
}
|
||||
@@ -2,7 +2,7 @@
|
||||
"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",
|
||||
"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",
|
||||
|
||||
@@ -2,10 +2,10 @@
|
||||
"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",
|
||||
"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",
|
||||
"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",
|
||||
|
||||
@@ -1,13 +1,13 @@
|
||||
{
|
||||
"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",
|
||||
"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 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.",
|
||||
"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",
|
||||
@@ -28,8 +28,8 @@
|
||||
"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_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.",
|
||||
|
||||
@@ -1,24 +1,24 @@
|
||||
{
|
||||
"tlMusdb": {
|
||||
"pageTitle": "musdb :: museum-digital",
|
||||
"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",
|
||||
"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 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>",
|
||||
"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:<\/p>\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. 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 <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 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>",
|
||||
"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<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 PHP7 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>.",
|
||||
"development_text": "Musdb is based on PHP7 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",
|
||||
"videos_and_screencasts": "Videos on YouTube",
|
||||
"in_blog": "News About the Development of musdb",
|
||||
"screenshot_dashboard_alt": "Dashboard \/ default startpage 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_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.",
|
||||
@@ -26,20 +26,20 @@
|
||||
"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_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_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_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_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_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_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."
|
||||
}
|
||||
}
|
||||
@@ -2,8 +2,8 @@
|
||||
"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",
|
||||
"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."
|
||||
"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."
|
||||
}
|
||||
}
|
||||
@@ -2,7 +2,7 @@
|
||||
"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",
|
||||
"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.",
|
||||
|
||||
@@ -2,13 +2,13 @@
|
||||
"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",
|
||||
"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",
|
||||
"license_usage": "License\/Usage",
|
||||
"authors": "Author(s)"
|
||||
}
|
||||
}
|
||||
@@ -1,10 +1,10 @@
|
||||
{
|
||||
"tlTerminology": {
|
||||
"pageTitle": "Terminological Work at museum-digital :: museum-digital",
|
||||
"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",
|
||||
"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_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>"
|
||||
}
|
||||
|
||||
Reference in new issue
Block a user