{
    "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 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 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."
    }
}