Docksr: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
We want to write an overlay for Google Drive that allows us to keep track of dependencies between documents. This GUI would show how documents are related (document A is a superclass of document B) and allow on-click access to these documents (via either Google Docs or Word). It will also enable document versioning (define document B to be a new version of document A) to allow us keep track of versions in a non-destructive way. | We want to write an overlay for Google Drive that allows us to keep track of dependencies between documents. This GUI would show how documents are related (document A is a superclass of document B) and allow on-click access to these documents (via either Google Docs or Word). It will also enable document versioning (define document B to be a new version of document A) to allow us keep track of versions in a non-destructive way. | ||
Some of this functionality already exists, so a big part of it this project would be to identify existing open source options and then customize it to run on top of Google Drive and our existing project management interface (Redmine). | Some of this functionality already exists, so a big part of it this project would be to identify existing open source options and then customize it to run on top of Google Drive and our existing project management interface ([http://www.redmine.org/ Redmine]). | ||
Why do we want to do this? The Berkman Center writes a lot of reports and academic papers. And when we write these reports, we then often generate a lot of other materials based on the original report (press releases, e-mails, websites, executive summaries, shorter versions of the report, etc.). When we write these smaller documents, we often need to use consistent language across all of the forms, which then creates significant problems when people make edits to a subsidiary documents. We need a way to keep track of documents and make sure that when changes occur in one, we know to also check all co-dependent documents. | Why do we want to do this? The Berkman Center writes a lot of reports and academic papers. And when we write these reports, we then often generate a lot of other materials based on the original report (press releases, e-mails, websites, executive summaries, shorter versions of the report, etc.). When we write these smaller documents, we often need to use consistent language across all of the forms, which then creates significant problems when people make edits to a subsidiary documents. We need a way to keep track of documents and make sure that when changes occur in one, we know to also check all co-dependent documents. | ||
Revision as of 13:34, 20 February 2015
We want to write an overlay for Google Drive that allows us to keep track of dependencies between documents. This GUI would show how documents are related (document A is a superclass of document B) and allow on-click access to these documents (via either Google Docs or Word). It will also enable document versioning (define document B to be a new version of document A) to allow us keep track of versions in a non-destructive way.
Some of this functionality already exists, so a big part of it this project would be to identify existing open source options and then customize it to run on top of Google Drive and our existing project management interface (Redmine).
Why do we want to do this? The Berkman Center writes a lot of reports and academic papers. And when we write these reports, we then often generate a lot of other materials based on the original report (press releases, e-mails, websites, executive summaries, shorter versions of the report, etc.). When we write these smaller documents, we often need to use consistent language across all of the forms, which then creates significant problems when people make edits to a subsidiary documents. We need a way to keep track of documents and make sure that when changes occur in one, we know to also check all co-dependent documents.