I agree with Florian that navigation of db contents is important and support is desirable - perhaps in analogy to file:children and file:descendants. Kind regards, Hans-Jürgen PS: The same applies to the contents of archives. Am Dienstag, 10. Mai 2022, 16:28:52 MESZ hat Florian Schmitt ml-basex@florian-schmitt.net Folgendes geschrieben:
Hi all,
i'm currently evaluating BaseX running on a headless Linux Server. It took me quite a while to get it running (the docs seem to be focused on Windows environments)... Is there a way to contribute to the documentation?
First question: After importing some of documents nicely organized in collections, i've found that the REST client will display all documents on the same "level" instead of showing just the first level of collections. This isn't nice if the db contains a great number of documents.... When accessing the same db using WebDAV (Oxygen), one can nicelly navigate using the collection structure. With REST, adding the collection names to the URL will restrict the output to the db content of those collections. But without such a restriction, it would be great if the REST web interface would just return the first level of collections without any XML resource entries.
Second question: What's the "best practice" for bulk imports while retaining the directory structure of the imported files using collections? I've found that Oxygen "translates" subdirectories into collections when using the "import directories" feature. Is there somehing similar using the command line client?
And another issue: The "Logs" page of the DBA webapp shows the following error warning:
"Unexpected error: Improper use? Potential bug? Your feedback is welcome: Contact..."
Is this a critical error? How to debug this? So far, i'found the wrapper-basex log, but it doesn't contain anything useful. Since i'm using the Yajsw Wrapper, there's no debug output or debug option (?).
Yours sincerely. Florian