Evaluate the features of ELNs (list provided) against 3 use cases

Project description: The final deliverable is an excel spreadsheet comparing the features of the following applications, with respect to their use as an electronic laboratory notebook within the context of three use-cases (a user with internet access; a user without internet access; a user that typically works without internet access, but occasionally works with internet access. In all three cases, users have a limited Windows account). RDIMS elabftw ELN described here: [login to view URL] paper-based laboratory notebook [login to view URL] [login to view URL] [login to view URL] [login to view URL] [login to view URL] [login to view URL] [login to view URL](eln) [login to view URL] [login to view URL] [login to view URL] [login to view URL] [login to view URL] Microsoft office suite [login to view URL] [login to view URL] [login to view URL] [login to view URL] [login to view URL] [login to view URL] [login to view URL] [login to view URL] [login to view URL] [login to view URL] [login to view URL] An ELECTRONIC lab notebook will be defined as software that aims to provide all of the features of a PAPER laboratory notebook, as defined on wikipedia ([login to view URL]) First draft due 1 week after accepting the project. Preliminary spreadsheet structure (which we must approve). This structure should demonstrate how you intend to structure your comparison, and include the list of applications being evaluated. Some software features should be listed, but the list does not need to be exhaustive at this stage. Some features, perhaps MOST features, may require that an unambiguous definition of that feature be explicitly stated; your preliminary spreadsheet should demonstrate how you intend to implement this. Features should include appearance, user-friendliness, ongoing development, support, security, platforms, whether an active internet connection is required for each feature, whether admin-level access to the O/S is required (for installation; or for usage of the software), initial cost, ongoing costs, where the data is stored, backups, interface languages, data entry languages that are supported, whether additional ( = not included in all Win7 basic installations) software must be installed, including plugins, windows components, libraries etc etc etc Second draft: due 1 week after after we approve your preliminary spreadsheet. You will then have one week in which to populate the spreadsheet. During this time, you will add to the list of attributes, create definitions for each attribute, and evaluate each software's performance against each attribute, for all three use cases. You will deliver this "intermediate deliverable" for our review and comment. You will address our comments. Third draft: due 1 week after we approve draft2 You will then have one more week to deliver the final deliverable, which incorporates our comments and includes the full evaluation of each software as well as a one-page description of each software. Preference will be given to coders who demonstrate that they have read this project description, and who confirm that they can deliver within these timelines, and who confirm specifically that they are available to do this work in October 2015. We will select a coder on Monday September 28.