Documentation for R&D work

[TiberiusB]

How should we deal with it?

• Should we mention documentation work in Labnotes? If that, then it cannot be easily searchable and quantifiable, but it becomes a resource that can be cited.
• Should it be logged as a non-production activity? If that, then there is no output created and no immediate association with the Labnotes. But time spent on it can be associated with it.

Other ideas?

During our meeting in Jun 17, we seemed to agree that logging documentation as an output is probably a better idea. This requires to create an output "document". These documents then become easier to filter out and data can be exported to the Role system.

[bhaugen]

If you will want to cite the document and use it for other processes, then log it as an output from the labnotes.

If you want to associate time directly with the document, add another work task to the labnotes process, take it yourself, and log both your time and the output document. (That will be easier soon.) Both the first and second labnotes as well as the original output and the document output will be tied together by the process.

If the document is not that important, then log it as non-production time and add the URL to the document.