Mercurial > hg > orthanc-book

comparison Sphinx/source/users/support.rst @ 276:3977ccfc318e

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
read log before asking support
author Sebastien Jodogne <s.jodogne@gmail.com>
date Tue, 03 Sep 2019 17:05:13 +0200
parents 1173e40cbf35
children 3d718457cfb6
comparison
equal deleted inserted replaced
275:2946fcd2e7fa 276:3977ccfc318e
10 10
11 When you face a problem, you should first check out the following 11 When you face a problem, you should first check out the following
12 resources: 12 resources:
13 13
14 1. Make sure to :ref:`understand the basics of DICOM <dicom-guide>`. 14 1. Make sure to :ref:`understand the basics of DICOM <dicom-guide>`.
15 2. Follow the :ref:`general troubleshooting guide <troubleshooting>`. 15 2. Carefully read your :ref:`log files in verbose mode <log>`.
16 3. If the problem is related to the DICOM network protocol, follow 16 3. Follow the :ref:`general troubleshooting guide <troubleshooting>`.
17 4. If the problem is related to the DICOM network protocol, follow
17 the :ref:`DICOM troubleshooting guide <dicom>`. 18 the :ref:`DICOM troubleshooting guide <dicom>`.
18 4. Have a look at **all** the :ref:`frequently asked questions (FAQs) 19 5. Have a look at **all** the :ref:`frequently asked questions (FAQs)
19 <faq>` that are already available in the Orthanc Book. 20 <faq>` that are already available in the Orthanc Book.
20 5. Make a search for similar problem previously discussed in the 21 6. Make a search for similar problem previously discussed in the
21 `Orthanc Users discussion forum 22 `Orthanc Users discussion forum
22 <https://groups.google.com/forum/#!forum/orthanc-users>`__. 23 <https://groups.google.com/forum/#!forum/orthanc-users>`__.
23 6. Check out the ``Pending changes in the mainline`` section of the 24 7. Check out the ``Pending changes in the mainline`` section of the
24 `NEWS file 25 `NEWS file
25 <https://bitbucket.org/sjodogne/orthanc/src/default/NEWS>`__, as 26 <https://bitbucket.org/sjodogne/orthanc/src/default/NEWS>`__, as
26 your issue might already be solved in the mainline of Orthanc (i.e. 27 your issue might already be solved in the mainline of Orthanc (i.e.
27 in the cutting-edge version of Orthanc since the last stable 28 in the cutting-edge version of Orthanc since the last stable
28 official release). 29 official release).
29 7. Carefully read the `TODO file 30 8. Carefully read the `TODO file
30 <https://bitbucket.org/sjodogne/orthanc/src/default/TODO>`__ that 31 <https://bitbucket.org/sjodogne/orthanc/src/default/TODO>`__ that
31 contains our roadmap, as you might be requesting a feature that is 32 contains our roadmap, as you might be requesting a feature that is
32 currently pending in our backlog (i.e. not implemented yet). 33 currently pending in our backlog (i.e. not implemented yet).
33 8. Have a look for the issue in the `official bug tracker 34 9. Have a look for the issue in the `official bug tracker
34 <https://bitbucket.org/sjodogne/orthanc/issues?status=new&status=open>`__ 35 <https://bitbucket.org/sjodogne/orthanc/issues?status=new&status=open>`__
35 (click on the ``All`` button, as your issue might already been solved). 36 (click on the ``All`` button, as your issue might already been solved).
36 37
37 38
38 Importantly, for all the features that are pending in the ``TODO`` 39 Importantly, for all the features that are pending in the ``TODO``