[MCN-L] Using barcodes and tablets
Great question Cris, We use labels with QR codes to track media hardware that we use in our exhibits. These QR codes are directly linked to a online database tool that we've built for tracking components, graphics, hardware, and objects in various exhibit projects. We currently only use the QR codes on media hardware, but have plans to expand this in the future. I know you're focused more on museum objects, but I think the process could be somewhat similar. Here's our workflow: 1. Create a new entry for a thing in our web tool. This generates a webpage with a unique URL, e.g. http://example.com/fake-exhibit/components/hardware/7896789 We generally do this in our planning stage before we actually purchase or acquire the asset. 2. Get the thing (monitor, computer, etc) 3. Update the online database entry with any new information. The URL for this entry still stays the same but any changes to the entry are versioned and trackable. 4. Generate a QR code for the URL. Since the URL will always stay the same (or get redirected) this QR code will always link to the online entry. 5. Use a computer connected label maker to print an adhesive label for the thing. 6. Stick it to the thing. The label still contains human readable data that would allow you to match up the device with the entry even if the QR code or URL broke (even though, we are committed to making sure they don't). During installs, inventory work, repairs, various staff can use any camera enabled device (tablet, phone, computer with camera) to look up the database entry for the thing. They can also update this in place. It's nice to be able to be up on a lift, scan a projector barcode, and update the database entry with serial number or somesuch info. The key here is that the QR code is equivalent to the URL and the URL is equivalent to the database entry for the thing. I think we're working to re-invent the URL sometimes. It's a great canonical identifier for things, as long as you remember Cool URIs don't change - http://www.w3.org/Provider/Style/URI.html . But this does require a develop for the web first mentality, which I understand is far from the norm in the collections management world. Looking forward to critiques of our process or examples from others, bk bryan kennedy director, exhibit media science museum of minnesota bkennedy at smm.org 651.221.2522 On Wed, May 29, 2013 at 2:44 PM, Cris Baczek cris.baczek at umfa.utah.eduwrote: Hello, My museum currently uses barcodes to track objects. We do ongoing inventories of our collections where we take a hand-held scanner, scan the barcode for a location, scan multiple barcodes for objects in that location, download the scanner data to a desktop computer, and upload this data (a .txt file) to our CMS database. This workflow works but it requires multiple steps during which data may be lost and time isn't used as efficiently as possible. We are researching how to go from this multi-step, multi-device method to a wireless workflow where a scanner would communicate through Bluetooth to a tablet and seamlessly update object location information. Is there anyone working this way? If so, I am interested in your workflow and the hardware and software you utilize. Many thanks, Cris Baczek cbaczek at umfa.utah.edumailto:cbaczek at umfa.utah.edu Collections Photographer Digital Media Producer Utah Museum of Fine Arts t: 801.585.0125 ___ You are currently subscribed to mcn-l, the listserv of the Museum Computer Network (http://www.mcn.edu) To post to this list, send messages to: mcn-l at mcn.edu To unsubscribe or change mcn-l delivery options visit: http://mcn.edu/mailman/listinfo/mcn-l The MCN-L archives can be found at: http://toronto.mediatrope.com/pipermail/mcn-l/
[MCN-L] Looking for help developing an RFP for a semi-mobile kiosk solution
We?d like to pick your brains about the best way to approach a new digital project at the Smithsonian! The Smithsonian Institution Traveling Exhibition Service (SITES) is considering the development of a mobile website and/or tablet application for visitors to its upcoming exhibition, Hometown Teams: How Sports Shape America. The exhibition explores the importance of sports in American life and the impact of sports on culture, communities, and on American character and values. The website and/or application would allow visitors to the exhibition galleries to navigate through text, images and video of game-day experiences at athletic events. The website and/or application would be required to operate in kiosk mode for continued use, work without continuous network access (as not all exhibition venues will have wifi or cellular data network coverage), and allow SITES staff to make content changes and reload a new version of the website or app to the device on an annual basis. SITES plans to reuse and build on this solution for the kiosk requirements of future traveling exhibitions as well. The project must be completed by January 15, 2014 and will be used throughout the life of the exhibition, Hometown Teams, which will travel to up to 180 communities in 30 states before retiring in 2020. Hometown Teams is a project of the Museum on Main Street program, a special collaboration between the Smithsonian and state humanities councils to provide exhibitions and programmatic expertise for small and rural cultural organizations. Here are some of our draft functional requirements; we?d love to hear your suggestions on these and others! - a web-based, user friendly content management system interface that allows the Smithsonian to change content easily, publish a new version of the app or website, and load it on to the devices that will be installed in the exhibition, either individually or en masse, via wifi or a cellular data network ? when Internet access is available! - open source technology and/or reusable components are preferred. - a fun and colorful interface inspired by the exhibition design, but developed in a template-driven way so that the kiosk?s look and feel can be customize for use with for other projects and devices in future. ability to collect analytics on kiosk use, even if just partial. Please note that Internet connectivity will not be continuous, so the analytics solution should be able to store usage data locally on the device until it can synch with a web-based analytics collection and reporting tool. - compliance with W3C web accessibility standards, supporting resizing of text, Voice Over or similar text to speech functionality, and video captioning as well as navigational buttons that are usable by people with reduced mobility in their hands and fingers. How Would You Do It? Here are some of our questions about the developing the solution; what else should we be asking? - Would you propose that the Smithsonian develop a mobile website or standalone application to achieve its goals? - Would you suggest we utilize open source programming and reusable components? - How long would it take to develop the initial kiosk product? - What methods and tools would you suggest for collecting usage metrics, especially given that the kiosks can?t be always connected to the Internet? - What kind of content management system would allow the Smithsonian to alter content each year most efficiently? - What standards should the project employ to ensure future portability of the product and content to other platforms and uses? We hope to issue a request for proposals (RFP) for this project in the next few weeks and will include a link to it here when it is published: http://smithsonian20.wordpress.com/2013/05/30/help-us-design-a-kiosk-solution-for-the-smithsonians-traveling-exhibitions-and-more/ Many thanks for your help! Nancy -- Nancy Proctor, PhD Head of Mobile Strategy Initiatives Office of the Assistant Secretary for Education and Access Smithsonian Institution http://si.edu/mobile proctorn at si.edu @nancyproctor t: +1-202-633-8439 c: +1-301-642-6257 Want to hear more about mobile? * Smithsonian staff can sign up for the SI Mobile mailing list here: http://si-listserv.si.edu/cgi-bin/wa?SUBED1=SIMOBILE * For global mobile news join the mailing list here: http://wiki.museummobile.info/ * Follow the museum mobile community on Twitter: #mtogo #SImobile To unsubscribe from the SIMOBILE list, or change your subscription options, please click here: http://si-listserv.si.edu/cgi-bin/wa?SUBED1=SIMOBILEA=1
[MCN-L] Using barcodes and tablets
On 30/05/2013 16:32, bryan kennedy wrote: The key here is that the QR code is equivalent to the URL and the URL is equivalent to the database entry for the thing. I think we're working to re-invent the URL sometimes. It's a great canonical identifier for things, as long as you remember Cool URIs don't change - http://www.w3.org/Provider/Style/URI.html . But this does require a develop for the web first mentality, which I understand is far from the norm in the collections management world. Excellent post, Bryan. I would strongly support the idea of using URLs as canonical identifiers. Interesting that you provide an updateable HTML view of the information, rather than a read only one. While no museum collection I know of has started off with URLs like yours for collections objects, it is possible to retro-fit a Linked Data view on to existing catalogue frameworks. Thus for example: http://collections.wordsworth.org.uk/Object/WTcoll/id/GRMDC.C104.4 is a persistent identifier for the Wordsworth Trust's object with accession/identity number GRMDC.C104.4. In addition, you can take advantage of content negotiation to get added value from this single identifier, so that it delivers you XML, RDF or even an image, via 303 See Other redirects to: http://collections.wordsworth.org.uk/Object/WTcoll/id/xml/GRMDC.C104.4 http://collections.wordsworth.org.uk/Object/WTcoll/id/rdf/GRMDC.C104.4 http://collections.wordsworth.org.uk/Object/WTcoll/id/jpeg/GRMDC.C104.4 respectively. Richard -- *Richard Light*
[MCN-L] Using barcodes and tablets
Richard, that's cool to hear that this isn't a totally heretical idea. Regarding your concern about read-only vs editable. It is easy to control this with either permissions, or a flag on the URL that allows you to see a specific revision on the edit. http://example.com/fake-exhibit/components/hardware/7896789?v=12 bk bryan kennedy director, exhibit media science museum of minnesota bkennedy at smm.org 651.221.2522 On Thu, May 30, 2013 at 11:38 AM, Richard Light richard at light.demon.co.ukwrote: On 30/05/2013 16:32, bryan kennedy wrote: The key here is that the QR code is equivalent to the URL and the URL is equivalent to the database entry for the thing. I think we're working to re-invent the URL sometimes. It's a great canonical identifier for things, as long as you remember Cool URIs don't change - http://www.w3.org/Provider/**Style/URI.htmlhttp://www.w3.org/Provider/Style/URI.html . But this does require a develop for the web first mentality, which I understand is far from the norm in the collections management world. Excellent post, Bryan. I would strongly support the idea of using URLs as canonical identifiers. Interesting that you provide an updateable HTML view of the information, rather than a read only one. While no museum collection I know of has started off with URLs like yours for collections objects, it is possible to retro-fit a Linked Data view on to existing catalogue frameworks. Thus for example: http://collections.wordsworth.**org.uk/Object/WTcoll/id/GRMDC.**C104.4http://collections.wordsworth.org.uk/Object/WTcoll/id/GRMDC.C104.4 is a persistent identifier for the Wordsworth Trust's object with accession/identity number GRMDC.C104.4. In addition, you can take advantage of content negotiation to get added value from this single identifier, so that it delivers you XML, RDF or even an image, via 303 See Other redirects to: http://collections.wordsworth.**org.uk/Object/WTcoll/id/xml/**GRMDC.C104.4http://collections.wordsworth.org.uk/Object/WTcoll/id/xml/GRMDC.C104.4 http://collections.wordsworth.**org.uk/Object/WTcoll/id/rdf/**GRMDC.C104.4http://collections.wordsworth.org.uk/Object/WTcoll/id/rdf/GRMDC.C104.4 http://collections.wordsworth.**org.uk/Object/WTcoll/id/jpeg/** GRMDC.C104.4http://collections.wordsworth.org.uk/Object/WTcoll/id/jpeg/GRMDC.C104.4 respectively. Richard -- *Richard Light* ___ You are currently subscribed to mcn-l, the listserv of the Museum Computer Network (http://www.mcn.edu) To post to this list, send messages to: mcn-l at mcn.edu To unsubscribe or change mcn-l delivery options visit: http://mcn.edu/mailman/listinfo/mcn-l The MCN-L archives can be found at: http://toronto.mediatrope.com/pipermail/mcn-l/
[MCN-L] software engineer
SOFTWARE ENGINEER (Web) Seattle Art Museum (see http://www.seattleartmuseum.org/ for application) OVERVIEW:Provide technical leadership, analysis, design and programming support for the implementation and extension of Museum Internet / SAM Intranet web sites and web applications. Provide maintenance and extension support for the Museum's proprietary Events Management System and the Gallery Systems eMuseum web extensions FLSA STATUS:Exempt REPORTS TO: Director, Information Technology ESSENTIAL FUNCTIONS: 1. Working with users and internal developers on various web development technologies, particularly Microsoft SharePoint based software solutions Develop custom software applications that interface with existing and new applications. 2. Training and support for users on how to leverage existing SharePoint technologies, maintenance and administration of the SharePoint farm, development of new and existing applications in SharePoint, and maintaining documentation of SharePoint based solutions. 3. Develop requirement documents for proposed modifications to existing applications or for proposed new applications. 4. Write application documents such as user guides, data definitions and data maintenance standards. 5. Advise Systems Engineer and Help Desk in the assignment of access rights for new or updated applications 6. Train or arrange for training users in the use of application computerized and manual procedures. 7. Advise Systems Engineer and Help Desk in developing backup and recovery plans for new or updated applications. 8. Work closely with other IT staff to ensure the integrity and security of application databases; Work closely with other IT staff to test, commission and install new or upgraded applications. 9. Perform other duties as assigned or as needed. QUALIFICATIONS, KNOWLEDGE, SKILLS, AND ABILITIES REQUIRED: 1. Bachelors in Computer Science or related technical field, or minimum of 5 years of applicable working experience. 2. Knowledge of SharePoint 2007-2013 technologies such as SharePoint Designer, InfoPath, Enterprise Search, Business Connectivity Services, Web Parts, Content Types, SharePoint Management Shell, etc. 3. Excellent understanding of SharePoint architecture and Features 4. A minimum of 5 years as a software developer, including 3 years of experience developing SharePoint 2007-2013 solutions. 5. Must be available to work on-site 5 days a week (Monday through Friday). 6. Working knowledge of business software in a setting similar to the Museum; for instance constituent management, collection management, digital asset management software applications. 7. Proficiency with one or more object oriented programming languages used by the Museum, such as C#, Visual Basic. 8. Proficiency in developing and maintaining database driven websites; eCommerce experience is preferable. 9. Proficiency with current versions of Windows, Microsoft Office products and programming systems including Visual Studio, SQL Server, Crystal Reports and SQL Reporting Services. 10. Experienced in developing applications that are based upon MS SQL 2005-2012. Must be able to design tables, views, queries and stored procedures. 11. Proficiency with CSS, HTML, HTML 5, XML, XSL, JavaScript, Jquery, ASP, ASP.NET web development technologies and tools. 12. Experience with all phases of the software development life cycle from Conceptualization through Maintenance 13. Desirable skills include a experience implementing Google Analytics services for a web site; use of Visio as a documentation tool and an understanding of the use of the Microsoft Access system as an application front end. 14. Ability to effectively prioritize and execute tasks in a high-pressure environment 15. Ability to think strategically. 16. Proven analytical and creative problem-solving abilities. 17. Superior interpersonal, verbal and written communications skills 18. Ability to communicate ideas in both technical and user-friendly language. 19. Strong customer service orientation 1. Ability to adapt to changes in the work environment and deal with frequent change or unexpected events 2. Must be highly organized, able to work without a high degree of supervision. 3. Must be able to maintain extremely high standards of confidentiality. 4. Must have the ability to use sound judgment on sensitive issues. 5. Ability to work professionally and tactfully and support management decisions in a positive, professional manner. WORKING CONDITIONS: Work areas are inside, in a climate-controlled environment with light background noise. PHYSICAL ACTIVITIES REQUIRED TO PERFORM ESSENTIAL FUNCTIONS: Sitting/Standing/Walking: Approximately 67% of time is spent working at a desk. Balance of time (approximately 33%) is spent moving around work areas. Speaking/Hearing: Ability
