Merge branch 'f-output' into 'dev'

MAINT: be more specific with output

See merge request !4

README_SETUP.md

@@ -34,7 +34,7 @@ For testing:
 3. Start an empty (!) CaosDB instance (with the mounted extroot). The
    database will be cleared during testing, so it's important to use
    an empty instance.
-4. Run `test.sh`.
+4. Run `test.sh`.  Note that this may modify content of the `integrationtest/extroot/` directory.
 
 ## Code Formatting
 `autopep8 -i -r ./`

integrationtests/crawl.py

@@ -43,7 +43,7 @@ except ModuleNotFoundError:
         return argparse.ArgumentParser()
 
     def print_success(text):
-        print("Success: "+text)
+        print("Success: " + text)
 
 
 def get_parser():

integrationtests/extroot/DataAnalysis/2010_TestProject/2019-02-03/README.md

 ---
 responsible:	
 - Only Responsible
-description: 	A description of another example analysis.
+description: 	A description of this example analysis.
 
 sources:
 - file:	"/ExperimentalData/2010_TestProject/2019-02-03/*.dat"

integrationtests/extroot/ExperimentalData/2010_TestProject/2019-02-03/README.md

 ---
 responsible:	
 - Only Responsible
-description: 	A description of another example experiment.
+description: 	A description of this example experiment.
 
 results:
 - file:	"/ExperimentalData/2010_TestProject/2019-02-03/*.dat"

integrationtests/extroot/Publications/Posters/2019-02-03_really_cool_finding/README.md

 ---
 responsible:	
 - Only Responsible
-description: 	A description of another example experiment.
+description: 	A description of this example experiment.
 
 sources:
 - /DataAnalysis/2010_TestProject/2019-02-03/results.pdf

integrationtests/extroot/SimulationData/2010_TestProject/2019-02-03/README.md

 ---
 responsible:	
 - Only Responsible
-description: 	A description of another example experiment.
+description: 	A description of this example experiment.
 
 results:
 - file:	"*.dat"

setup.py

@@ -155,8 +155,8 @@ def setup_package():
         author='Henrik tom Wörden',
         author_email='h.tomwoerden@indiscale.com',
         install_requires=["caosdb>=0.4.0",
-                          "openpyxl>=3.0.0",
-                          "xlrd==1.2.0",
+                          "pandas>=1.2.0",
+                          "xlrd>=2.0",
                           ],
         packages=find_packages('src'),
         package_dir={'': 'src'},

src/caosadvancedtools/crawler.py

@@ -310,8 +310,6 @@ class Crawler(object):
         if self.interactive and "y" != input("Do you want to continue? (y)"):
             return
 
-        logger.info("Inserting or updating Records...")
-
         for cfood in cfoods:
             try:
                 cfood.create_identifiables()
@@ -544,6 +542,10 @@ carefully and if the changes are ok, click on the following link:
 
         logger.debug(cfood.to_be_updated)
         try:
+            if len(cfood.to_be_updated) > 0:
+                logger.info(
+                        "Updating {} Records...".format(
+                            len(cfood.to_be_updated)))
             guard.safe_update(cfood.to_be_updated, unique=False)
         except FileNotFoundError as e:
             logger.info("Cannot access {}. However, it might be needed for"
@@ -605,6 +607,9 @@ carefully and if the changes are ok, click on the following link:
             logger.debug("No new entities to be inserted.")
         else:
             try:
+                logger.info(
+                    "Inserting {} Records...".format(
+                        len(missing_identifiables)))
                 guard.safe_insert(missing_identifiables, unique=False)
             except Exception as e:
                 DataModelProblems.evaluate_exception(e)

src/doc/crawler.rst

@@ -75,7 +75,7 @@ The crawler can be executed directly via a python script (usually called
 ``crawl.py``). The script prints the progress and reports potential
 problems. The exact behavior depends on your setup. However, you can
 have a look at the example in the
-`tests <https://gitlab.com/caosdb/caosdb-advanced-user-tools/-/blob/main/integrationtests/full_test/crawl.py>`__.
+`tests <https://gitlab.indiscale.com/caosdb/src/caosdb-advanced-user-tools/-/blob/main/integrationtests/crawl.py>`__.
 
 .. Note:: The crawler depends on the CaosDB Python client, so make sure to install :doc:`pycaosdb
           <caosdb-pylib:getting_started>`.
@@ -86,14 +86,18 @@ Typically, an invocation looks like:
 
 .. code:: python
 
-   python3 crawl.py "/TestData/"
+   python3 crawl.py /someplace/
 
-In this case ``/TestData/`` identifies the path to be crawled **within
-the CaosDB file system**. You can browse the CaosDB file system by
+.. Note:: For trying out the above mentioned example crawler from the integration tests,
+          make sure that the ``extroot`` directory in the ``integrationtests`` folder is used as
+          CaosDB's extroot directory, and call the crawler indirectly via ``./test.sh``.
+
+In this case ``/someplace/`` identifies the path to be crawled **within
+CaosDB's file system**. You can browse the CaosDB file system by
 opening the WebUI of your CaosDB instance and clicking on “File System”.
 
 In the backend, ``crawl.py`` starts a CQL query
-``FIND File WHICH IS STORED AT /TestData/**`` and crawls the resulting
+``FIND File WHICH IS STORED AT /someplace/**`` and crawls the resulting
 files according to your customized ``CFoods``.
 
 Crawling may consist of two distinct steps: 1. Insertion of files (use