-
Notifications
You must be signed in to change notification settings - Fork 11
Working with Mayan
cccs-ip edited this page Aug 6, 2014
·
8 revisions
To setup Mayan EDMS from scratch the first thing to consider are which are going to be your document types. Examples of document types are: Legal documents, Internal documents, Medical records, Designing specifications, Permits. A document type represent a group, a type, a class of documents which share some common properties. A good indicator that can help you determine you document types is what kind of information or metadata is attached to the documents.
Bibliography entries included in a .bib file are split by types. The following types are understood by virtually all BibTeX styles:
| Entry Type | Description | Required Data Field | Optional Data Field | Notes |
|---|---|---|---|---|
| article | An article from a journal or magazine. | Required fields: author, title, journal, year; | Optional fields: volume, number, pages, month, note, key | |
| book | A book with an explicit publisher. | Required fields: author/editor, title, publisher, year; | Optional fields: volume/number, series, address, edition, month, note, key | |
| booklet | A work that is printed and bound, but without a named publisher or sponsoring institution. | Required fields: title; | Optional fields: author, howpublished, address, month, year, note, key | |
| conference | The same as inproceedings, included for Scribe compatibility. | |||
| inbook | A part of a book, usually untitled. May be a chapter (or section, etc.) and/or a range of pages. | Required fields: author/editor, title, chapter/pages, publisher, year; | Optional fields: volume/number, series, type, address, edition, month, note, key | |
| incollection | A part of a book having its own title. | Required fields: author, title, booktitle, publisher, year; | Optional fields: editor, volume/number, series, type, chapter, pages, address, edition, month, note, key | |
| inproceedings | An article in a conference proceedings. | Required fields: author, title, booktitle, year; | Optional fields: editor, volume/number, series, pages, address, month, organization, publisher, note, key | |
| manual | Technical documentation. | Required fields: title; | Optional fields: author, organization, address, edition, month, year, note, key | |
| mastersthesis | A Master's thesis. | Required fields: author, title, school, year; | Optional fields: type, address, month, note, key | |
| misc | For use when nothing else fits. | Required fields: none; | Optional fields: author, title, howpublished, month, year, note, key | |
| phdthesis | A Ph.D. thesis. | Required fields: author, title, school, year; | Optional fields: type, address, month, note, key | |
| proceedings | The proceedings of a conference. | Required fields: title, year; | Optional fields: editor, volume/number, series, address, month, publisher, organization, note, key | |
| techreport | A report published by a school or other institution, usually numbered within a series. | Required fields: author, title, institution, year; | Optional fields: type, number, address, month, note, key | |
| unpublished | A document having an author and title, but not formally published. | Required fields: author, title, note; | Optional fields: month, year, key |