Resource: The Marriage of Standards and Access: Centralized Services as a Tool for Collaboration, Publication and Curation
By Elijah Meeks
…This is fundamentally an argument directed at administrators looking to support digital humanities work at their universities and not researchers looking to perform digital humanities work, but it is meant to push that latter group toward agitating for action from the former. I’ve had enough experience now with digital humanities projects to know that when you’re collaborating with computer scientists or contracting developer resources without a sense of standardized, centralized resources, then the data, code and tool decisions tend to be made based on expediency or a desire to experiment with new, unsupported and/or experimental technologies.