Reference+Review+Database

=Reference Review Database (Reference Review) (GWU EMSE 216-8000)=

Index | Topics | Lectures | Course Work | Reference

The prototye database is based on a spreadsheet provided by Patrice Jackson. It is still in development and initial test. After a little testing it will be posted. It could be jused just for the literature relevance tracking, or, annotating that a document has been collected, or, categorizing the notes by category to aid finding common ideas later ( TBD ).

Phil is not very sure that it will be easy enough to use, but thinks having notes and references organized digitally might make it worthwhile. One idea is that notes could be presented for review during writing by category and that organizing the literature reveiw by category might be a good approach.



The Literature Review Database can be used
 * First, with consolidated //Cittaton// information --> quicker data entry for potential sources that don't make the cut early on
 * Later, with //Publication// data (for eventual {hopefully} import into EndNote. //PubType// is not required, but might be useful for a qualtiy of source indicator (TBD). //PubVersion// is used wtih periodicals.
 * The //Abstract// can be stored in the database along with the //Reference// and //Note//(s) that are taken.
 * //Relevance// can be captured for Literature Review //Categories.//
 * Data //Categories// might be useful for the full literature review. They probably could match the categories in the Data Requirements matrix.
 * Hypotheses from the matrix by be another type of review categories.
 * [[image:Lit_Review_Database_-_Categories.JPG width="230" height="319"]]
 * The //CheckList// is to keep track of things.
 * References to incldue in the bibliography
 * Perhaps things that need to be done later
 * i.e. if reviewing references at a summary level to determine the best, which one's need to be review at the notes level
 * The checklist creates a many-to-many relationship between the reference and checklist categories (CheckCatg) so new items can be added without changing the underlying database structure.
 * //Cited// (TBD) may provide a way of keeping track of the reference hierachry within the LitReview Database. Not sure, but I can see where it might be userful in following references back to the earliest source.


 * Sources**
 * TBD

Contributors: Sisson