-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
First draft for en/getting-started.md #297
Changes from all commits
07921cf
484bbc8
f3b8348
0575a93
981461d
8617975
caa77cf
621b69c
5dde449
3b0337a
758e3d2
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||||
---|---|---|---|---|---|---|---|---|
@@ -1,10 +1,116 @@ | ||||||||
# Getting started | ||||||||
|
||||||||
## Main Window of JabRef | ||||||||
|
||||||||
Upon the first start of JabRef the main user interface is showing up the main elements are: | ||||||||
|
||||||||
- Menu bar | ||||||||
- Icon bar (shortcuts for most frequently used features) | ||||||||
- Side bar (for groups and web search) | ||||||||
|
||||||||
![Screenshot of main window](.gitbook/assets/getting-started-main-screen.png) | ||||||||
|
||||||||
## Creation of a new library | ||||||||
|
||||||||
A "library" is the main file that saves all the information about your collection of references. The storage format of the file is text-based in the Bibtex standard. | ||||||||
|
||||||||
{% hint style="info" %} | ||||||||
The usage of a text-based file format has some advantages: | ||||||||
|
||||||||
- The file is "human readable" and editable with every text editor | ||||||||
- the text format allows for an easy tracking of changes with every common version control protocol (e.g., git) | ||||||||
- and finally: the format is dedicated for the usage with LaTeX; so you do not need to convert it to any other format but you can just directly link to your JabRef library | ||||||||
|
||||||||
{% endhint %} | ||||||||
|
||||||||
To create a new library, just select the "New library" menu item in the "File" menu: | ||||||||
|
||||||||
![Creating a new library](.gitbook/assets/getting-started-new-library.png) | ||||||||
|
||||||||
The main screen is now showing an empty "entry table" we will now start to fill with some entries. | ||||||||
|
||||||||
## Adding of a new entry manually | ||||||||
|
||||||||
To add a new entry select the menu bar entry "Library" -> "New entry", click on the icon in the icon bar, or just hit CTRL-N. | ||||||||
|
||||||||
This opens a dialog where you can select the type of reference you want to store. By default all entry types defined by the Bibtex format are available: | ||||||||
|
||||||||
![Screenshot of "new entry" dialog](.gitbook/assets/getting-started-new-entry.png) | ||||||||
|
||||||||
For our running example we will select "Article". | ||||||||
|
||||||||
After clicking on the "Article" button, the dialog closes and the so called "Entry Editor" is opened for the newly created entry: | ||||||||
|
||||||||
![Main window now showing the entry editor](.gitbook/assets/getting-started-entry-editor.png) | ||||||||
|
||||||||
The most important information about the references to be added can now be entered in the "Required Fields" tab. | ||||||||
"Author", "Title", "Journal", and "Year" should be self-explanatory - however, a "citationkey", might not be familiar to you. | ||||||||
Basically, the idea of the "citationkey" (formerly called "bibtexkey") is coming from working with Bibtex, where it is necessary to have an unique identifier for each entry. This allows for referencing within a document you might be creating using the stored information in your library. Moreover, also within JabRef this "key" is used for example for cross-references to other related entries or to determine file names for full-text references. | ||||||||
|
||||||||
The key usually follows a global pattern and can be easily created automatically by clicking on the "generate" button next to the field. | ||||||||
|
||||||||
{% hint style="info" %} | ||||||||
Coming soon! | ||||||||
The default key pattern is `[auth][year]`, which means that Author information is followed by the year of the publication, resulting in the example in `Turing1950`. However, the key pattern is customizable to your needs. See [Configuration](https://docs.jabref.org/setup) > ["Customize the citation key generator"](https://docs.jabref.org/setup/bibtexkeypatterns) for more details. | ||||||||
{% endhint %} | ||||||||
|
||||||||
Desktop interface \(basic description of the user interface elements and what they do\) | ||||||||
After entering some information, you can see on the right side of the entry editor a preview of the bibliographic data: | ||||||||
|
||||||||
![Added information for new entry](.gitbook/assets/getting-started-filled-entry-editor.png) | ||||||||
|
||||||||
matthiasgeiger marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||||
There are further possibilities to add entries to your library which are described in the section "Collect" of this documentation: | ||||||||
|
||||||||
{% page-ref page="./collect" %} | ||||||||
|
||||||||
## Enhancing the information | ||||||||
|
||||||||
After creating the basic information the addition of all other bibliographical details is often cumbersome and error-prone. To ease this task, JabRef allows for an automatic completion of the bibliographic information by looking up the data in public databases. | ||||||||
To use this feature just click on the "Update with bibliographic information from the web" button in the editor: | ||||||||
|
||||||||
![Update information from web](.gitbook/assets/getting-started-entry-editor-update-from-web.png) | ||||||||
|
||||||||
{% hint style="info" %} | ||||||||
The found information is most accurate if an identifier like a "DOI" or "ISBN" is maintained. If you already know such an unique identifier, this can also be already the starting point to create a new entry without manual entering any information by using the "create from ID" feature in the Create entry dialog. For more information see: [Collect](https://docs.jabref.org/collect) > ["Add entry using an ID"](https://docs.jabref.org/collect/add-entry-using-an-id) | ||||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Maybe add a hint that you can paste DOIs direclty on the main table? |
||||||||
{% endhint %} | ||||||||
|
||||||||
If additional information is found you will be asked in a dialog which information should be taken over: | ||||||||
|
||||||||
![Merging the existing and the web information](.gitbook/assets/getting-started-merge-entries.png) | ||||||||
|
||||||||
## Adding a full text document | ||||||||
|
||||||||
Usually, you also want to attach a reference to the full-text of a reference. For this, you can use the "file" field in the "General" tab. | ||||||||
Here you can either attach a file manually, search for an already existing local file matching the bibtexkey pattern, or trying to automatically download a matching full text from the web. | ||||||||
|
||||||||
{% hint style="info" %} | ||||||||
In order to use the automated feature, it is necessary to set-up a file directory first. To do so, please go to "Options" > "Preferences", go to "File" section and select there an existing folder as the "Main file directory": | ||||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The default behavior is that JabRef looks for files relative to the bib file, so I would describe this in the getting started section, an then point them to the "Override file directories" section if they want to change that. If we need to point users to the preferences in "getting started", then we should change the default preferences in my opinion. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yep. That's a bug which was somehow introduced in 5.1. No idea how it came. |
||||||||
|
||||||||
![Setting up the main file directory](.gitbook/assets/getting-started-preferences.png) | ||||||||
{% endhint %} | ||||||||
|
||||||||
To test the automatic download of full texts you can click on the "Get full-text" icon next to the file field, or choose "Lookup" -> "Search full text documents online" from the menu. As soon as a full-text is found, the file will be stored in the local file directory and linked to the entry: | ||||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||||
|
||||||||
![Finding a full-text document online](.gitbook/assets/getting-started-entry-editor-full-text.png) | ||||||||
|
||||||||
To open the downloaded full text you can click on the "file" icon before the file name - or use the same icon in the entry table: | ||||||||
![Opening the full-text](.gitbook/assets/getting-started-open-fulltext.png) | ||||||||
|
||||||||
## Finding more references in the web | ||||||||
|
||||||||
If you want to search for other references, it is also possible to directly trigger a search in many of the most common bibliographic databases. To start a search just use the "Web Search" feature of JabRef: | ||||||||
First select one of the existing data sources, enter a search term and click on "search": | ||||||||
|
||||||||
The search results will be shown in an window where you can select all the search hits to be added to your library. | ||||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. That's not relevant for a getting started in my opinion There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I was referring to the dialog, that it has an option to download the ffull text . |
||||||||
|
||||||||
![Web Search: Trigger and result window](.gitbook/assets/getting-started-import-from-web.png) | ||||||||
|
||||||||
## Next steps | ||||||||
|
||||||||
After adding more and more entries, your library might be a bit too unstructured. In order to keep all you references organized JabRef is offering a lot of helpful features like grouping, consistency checks, etc. | ||||||||
|
||||||||
You can find more information on this topics in the "Organize" section of the documentation: | ||||||||
|
||||||||
{% page-ref page="./organize" %} | ||||||||
|
||||||||
Quick start \(basic userflow: create new library -> add entry, link file, do web search -> save\) | ||||||||
If you want to start writing your own papers, articles or thesis, you might find some helpful information on how to use JabRef for citing your collected references from your library: | ||||||||
|
||||||||
{% page-ref page="./cite" %} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would move this information about bibtex to https://docs.jabref.org/cite/bibtex-and-biblatex. It's not utterly important for a new user how JabRef saves his information (except when he starts to cite papers in tex).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As this is for me still one of the essential aspects of JabRef I would keep it ;-)