This "internal" issue is about refactoring some functions between cernopendata-client components.
The searcher component is basically contacting CERN Open Data portal and its API. So it is meant as a web client for /api/records and friends.
Currently, the same component contains also get_list_directory() function, which is not exactly using the above search APIs, but it is rather working directly with the EOSPUBLIC /eos/opendata filesystem and directory structure.
This issue proposes to separate EOSPUBLIC directory handling functions (that are not using opendata.cern.ch's portal API in any way) into a new component.
We can invent some nice name, e.g. eospublic (but this is not a verb) or walker.py or filer.py (but this may be weird) or xrootdexplorer (for example) or something?
This "internal" issue is about refactoring some functions between
cernopendata-clientcomponents.The
searchercomponent is basically contacting CERN Open Data portal and its API. So it is meant as a web client for/api/recordsand friends.Currently, the same component contains also
get_list_directory()function, which is not exactly using the above search APIs, but it is rather working directly with the EOSPUBLIC/eos/opendatafilesystem and directory structure.This issue proposes to separate EOSPUBLIC directory handling functions (that are not using opendata.cern.ch's portal API in any way) into a new component.
We can invent some nice name, e.g.
eospublic(but this is not a verb) orwalker.pyorfiler.py(but this may be weird) orxrootdexplorer(for example) or something?