- These list items are microformat entries and are hidden from view.
- https://dltj.org/article/dpla-appfest-report/
- Below is my report of the DPLA AppFest last month. This post is the raw input of an article on the IMLS blog that was co-written with Mary Barnett, Social Media Coordinator at the Chattanooga Public Library. I also attended yesterday's DPLA Audience and Participation workstream meeting at George Mason University, and hope to have a similar trip report posted soon.The Digital Public Library of America held an AppFest gathering at the Chattanooga Public Library on November 8-9, 2012 for a full day of designing, developing and discussion. About 40 people attended from a wide range of backgrounds:Public libraries, academic libraries, companies, library consortia and other groups.Designers, user experience professions, metadata specialists, coders, and "idea people".A variety of U.S. states and Canadian provinces. One of the primary purposes of day was to test the DPLA application programming interface (API) to see if it could answer queries from programs that would do useful tasks. The quick answer to that challenge would seem to be "yes!" and there were a lot of positive feelings coming out of the meeting.The goal of the DPLA is a little unusual. Although there will be a public web-based interface to the DPLA content, the overriding desire is to build the back-end services that will enable DPLA content to be used through local libraries, archives and museums in a variety of interfaces. In this way, DPLA is like a traditional publisher: it will gather content from a variety of sources (authors), add new value (copyedit, create an index), and send out content through a variety of streams (libraries, local bookstores, internet retailers and other venues like convenience stores and airport shops). The DPLA will gather content from regional and subject hubs, enhance it, and make it available to websites, mobile applications, and other tools. So the AppFest was a way to figure out if the early technology designs of the DPLA could meet those goals.The AppFest started on Thursday evening with a recorded video welcome from John Palfrey and a recording of Emily Gore from DPLA Midwest introducing the DPLA Digital Hubs Pilot Program followed by a brief introduction to developer productivity tools Git and GitHub by Andromeda Yelton. The evening ended with people pitching ideas for projects that participants would work on the next day. The ideas were ones previously recorded on the DPLA wiki page or were spontaneously created at the meeting. [caption id="attachment_4049_picture" align="aligncenter" width="600"] Sign-up sheet for Appfest Projects[/caption]Friday morning started with an introduction to the DPLA API by Jeffrey Licht of Pod Consulting and a review of the possible projects. The project titles were put up on a wall and people self-selected what they wanted to work on for the day. I picked the project that wanted to create a map interface with pins that corresponded to the position of resources in the repository, and other choices were distributed reference services, visualization techniques to see collection content in context with the whole repository, and a new-content notification service. The teams presented their work at the end of the day to the other participants and a panel of judges. We even had a presentation from a remote participant show his work over a Skype video call. After much deliberation, the judges picked the "DPLA Plus" project as best of the AppFest; that project focused on the need of public users to discover what is in the repository.I think most would agree that the AppFest was a success. The API lived up to the challenge, both in terms of robustness of functionality and its technical ability to respond to queries from the projects. The records returned from the DPLA data set show the challenges of aggregating metadata from disparate sources. In our project we had problems with nonsensical geo-located records that could be filtered, checked and enhanced by automated routines at the central hub. We also ran into the classic difficulty of having reasonable thumbnails to display to users. Web addresses to thumbnail images are not a common part of metadata since they are usually created by the repository system itself. Having a DPLA service to augment records from hubs with URLs to real thumbnail images would be a very helpful addition.The AppFest was more evidence that the DPLA is definitely pulling itself up by its bootstraps. Coming a month after a successful Midwest plenary session and two months after formal incorporation and installation of its board of directors plus announcements of new rounds of grant funding from IMLS, NEH, and the Knight Foundation, the DPLA is making steady progress towards fulfilling its mission. The next major event is slated to be the unveiling of a public interface to the DPLA collection in April 2013.The text was modified to update a link from http://dp.la/get-involved/events/appfest/ to http://dp.la/info/developers/appfest/ on September 26th, 2013.The text was modified to update a link from http://dp.la/get-involved/events/dplamidwest/ to http://dp.la/info/get-involved/events/dplamidwest/ on September 26th, 2013.
- 2012-12-07T19:18:52+00:00
- 2018-01-15T20:28:01+00:00
Trip Report of DPLA Chattanooga Appfest: Project Shows Signs of Life
The Digital Public Library of America held an AppFest gathering at the Chattanooga Public Library on November 8-9, 2012 for a full day of designing, developing and discussion. About 40 people attended from a wide range of backgrounds:
- Public libraries, academic libraries, companies, library consortia and other groups.
- Designers, user experience professions, metadata specialists, coders, and "idea people".
- A variety of U.S. states and Canadian provinces.
One of the primary purposes of day was to test the DPLA application programming interface (API) to see if it could answer queries from programs that would do useful tasks. The quick answer to that challenge would seem to be "yes!" and there were a lot of positive feelings coming out of the meeting.
The goal of the DPLA is a little unusual. Although there will be a public web-based interface to the DPLA content, the overriding desire is to build the back-end services that will enable DPLA content to be used through local libraries, archives and museums in a variety of interfaces. In this way, DPLA is like a traditional publisher: it will gather content from a variety of sources (authors), add new value (copyedit, create an index), and send out content through a variety of streams (libraries, local bookstores, internet retailers and other venues like convenience stores and airport shops). The DPLA will gather content from regional and subject hubs, enhance it, and make it available to websites, mobile applications, and other tools. So the AppFest was a way to figure out if the early technology designs of the DPLA could meet those goals.
The AppFest started on Thursday evening with a recorded video welcome from John Palfrey and a recording of Emily Gore from DPLA Midwest introducing the DPLA Digital Hubs Pilot Program followed by a brief introduction to developer productivity tools Git and GitHub by Andromeda Yelton. The evening ended with people pitching ideas for projects that participants would work on the next day. The ideas were ones previously recorded on the DPLA wiki page or were spontaneously created at the meeting.
[caption id="attachment_4049_picture" align="aligncenter" width="600"]
Sign-up sheet for Appfest Projects[/caption]
Friday morning started with an introduction to the DPLA API by Jeffrey Licht of Pod Consulting and a review of the possible projects. The project titles were put up on a wall and people self-selected what they wanted to work on for the day. I picked the project that wanted to create a map interface with pins that corresponded to the position of resources in the repository, and other choices were distributed reference services, visualization techniques to see collection content in context with the whole repository, and a new-content notification service. The teams presented their work at the end of the day to the other participants and a panel of judges. We even had a presentation from a remote participant show his work over a Skype video call. After much deliberation, the judges picked the "DPLA Plus" project as best of the AppFest; that project focused on the need of public users to discover what is in the repository.
I think most would agree that the AppFest was a success. The API lived up to the challenge, both in terms of robustness of functionality and its technical ability to respond to queries from the projects. The records returned from the DPLA data set show the challenges of aggregating metadata from disparate sources. In our project we had problems with nonsensical geo-located records that could be filtered, checked and enhanced by automated routines at the central hub. We also ran into the classic difficulty of having reasonable thumbnails to display to users. Web addresses to thumbnail images are not a common part of metadata since they are usually created by the repository system itself. Having a DPLA service to augment records from hubs with URLs to real thumbnail images would be a very helpful addition.
The AppFest was more evidence that the DPLA is definitely pulling itself up by its bootstraps. Coming a month after a successful Midwest plenary session and two months after formal incorporation and installation of its board of directors plus announcements of new rounds of grant funding from IMLS, NEH, and the Knight Foundation, the DPLA is making steady progress towards fulfilling its mission. The next major event is slated to be the unveiling of a public interface to the DPLA collection in April 2013.
The text was modified to update a link from http://dp.la/get-involved/events/appfest/ to http://dp.la/info/developers/appfest/ on September 26th, 2013.
The text was modified to update a link from http://dp.la/get-involved/events/dplamidwest/ to http://dp.la/info/get-involved/events/dplamidwest/ on September 26th, 2013.
