> For the complete documentation index, see [llms.txt](https://docs.jabref.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jabref.org/v5/advanced/knowledge/msofficebibfieldmapping.md). # MS Office Bibliography XML format JabRef supports the MS Office Bibliography XML format for exporting and importing. ## Howto: Import from Microsoft Word See ## Entry Type Mappings Some field names in the XML format differ from the field names in the BibTeX/BibLaTeX format and can therefore be not directly mapped between the formats. Therefore this help file provides a list of all field mappings. | BibTeX/biblatex entry type | XML entry type | | -------------------------- | --------------------- | | book | Book | | inbook | BookSection | | booklet | BookSection | | incollection | BookSection | | article | JournalArticle | | inproceedings | ConferenceProceedings | | conference | ConferenceProceedings | | proceedings | ConferenceProceedings | | collection | ConferenceProceedings | | techreport | Report | | manual | Report | | mastersthesis | Report | | phdthesis | Report | | unpublished | Report | | patent | Patent | | misc | Misc | | electronic | ElectronicSource | | online | InternetSite | | periodical | ArticleInAPeriodical | ## Field mappings The field mapping for import and export is mostly the same, but there are some differences, as not all field exists in both formats. Additionally, some fields have to be treated differently during import/export. | BibTeX/BibLaTeX | XML field | | --------------- | ---------------------------------------- | | bibtexkey | Tag | | title | Title | | year | Year | | note | Comments | | volume | Volume | | language | LCID | | edition | Edition | | publisher | Publisher | | booktitle | BookTitle | | chapter | ChapterNumber | | issue | Issue | | school | Department | | institution | Institution | | doi | DOI | | url | url | | shorttitle | ShortTitle | | pages | Pages | | authors | Authors | | editors | Editors | | translator | Translator | | bookauthor | Bookauthor | | volumes | NumberVolumes | | urldate | YearAccessed, MonthAccessed, DayAccessed | ### BibTeX/BibLaTeX only fields The following fields are BibTeX/biblatex only fields, they have no representation in office XML. In the resulting XML file, they are represented with the prefix `BIBTEX_` | BibTeX/biblatex only fields | XML representation | | --------------------------- | -------------------- | | series | BIBTEX\_Series | | abstract | BIBTEX\_Abstract | | keywords | BIBTEX\_KeyWords | | crossref | BIBTEX\_CrossRef | | howpublished | BIBTEX\_HowPublished | | affiliation | BIBTEX\_Affiliation | | contents | BIBTEX\_Contents | | copyright | BIBTEX\_Copyright | | price | BIBTEX\_Price | | size | BIBTEX\_Size | | intype | BIBTEX\_InType | | paper | BIBTEX\_Paper | | \ | BIBTEX\_Entry | | \ | SourceType | | key (not bibtexkey) | BIBTEX\_KEY | | pubstate | BITEX\_Pubstate | The XML field `SourceType` contains the associated entry type from the first table, while the original BibTeX/BibLaTex entrytype is preserved in the field `BIBTEX_ENTRY`. ### MS-Bib only fields The following fields are XML-only fields, they have no BibTeX/biblatex representation: In the resulting bib database they are represented with the prefix `msbib-`. | BibTeX/BibLaTex represenation | XML field | | ----------------------------- | --------------------------------------------------- | | msbib-numberofvolume | NumberVolumes | | msbib-periodical | PeriodicalTitle | | msbib-day | Day | | msbib-accessed | Accessed (YearAccessed, MonthAccessed, DayAccessed) | | msbib-medium | Medium | | msbib-recordingnumber | RecordingNumber | | msbib-theater | Theater | | msbib-distributor | Distributor | | msbib-broadcaster | Broadcaster | | msbib-station | Station | | msbib-type | Type | | msbib-court | Court | | msbib-reporter | Reporter | | msbib-casenumber | CaseNumber | | msbib-abbreviatedcasenumber | AbbreviatedCaseNumber | | msbib-productioncompany | ProductionCompany | | msbib-producername | producerNames | | msbib-composer | composers | | msbib-conductor | conductors | | msbib-performer | performers | | msbib-writer | writers | | msbib-director | directors | | msbib-compiler | compilers | | msbib-interviewer | interviewers | | msbib-interviewee | interviewees | | msbib-inventor | inventors | | msbib-counsel | counsels | ### Special Export treatment The following fields are treated as follows during export: | BibTeX/biblatex representation | XML field | | ------------------------------------------------------------------ | ---------------------------------------------- | | booktitle | ConferenceName | | journal | JournalName | | journaltitle | JournalName | | month | Month | | date | year, month, day (if date is in ISO 8601 form) | | issue | issue | | isbn | StandardNumber | | issn | StandardNumber | | lccn | StandardNumber | | mrnumer | StandardNumber | | address (if field contains at least one comma) | City | | address (if field does not contain a comma) | City, StateProvince, CountryRegion | | location (if field contains at least one comma) | City | | location (if field does not contain a comma) | City, StateProvince, CountryRegion | | \ | ThesisType | | \ number | PatentNumber | | number (entry is not patent) | Number | | Authors/Editors (single author/editor is enclosed in curly braces) | Corporate | | author (if entry type is patent) | Inventor | ### Special Import treatment The following fields are treated as follows during import: | BibTeX/biblatex representation | XML field | | ------------------------------ | ---------------------------------- | | organization | ConferenceName | | journaltitle | Journal | | location | City, StateProvince, CountryRegion | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.jabref.org/v5/advanced/knowledge/msofficebibfieldmapping.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.