BaseX-Talk March 2021

basex-talk@mailman.uni-konstanz.de

16 participants
17 discussions

first post on this mailinglist
by commandline-be 17 Mar '21

17 Mar '21

Dear, With a need to dig into ms eventlog converted to xml i landed with BaseX and was amazed by the functionality presented with this tool. I'm new to many things here so i'm going thru a learning curve here. This mail is mostly to propose improvement and feature requests, some minor other may be more elaborate * Map visualisation : a mode in which the keys are listed in hierarchical yet isometric way so they are not abreviated but listed for visual acessibility. * Forms builder : a simple form builder to datamine xml files would be nice, for my current purpose i'm to write a number of queries to identify specific eventid, attributes and values in relation to one another, being able to simply select a query in a drop down would be nice to review results etc * Possible bug : the preferences dialog no longer shows up * upgrade path : working with a linux distro prohibits simple upgrading, an upgrade dialog for drop in out of band upgrades could prove welcome to not flood this mailing list old bugs Thank you, Joris

2 3

Simple xqdoc to HTML converter
by Omar Siam 15 Mar '21

15 Mar '21

Hi, I brushed up the 2006 xqdoc to HTML XQuery a bit to document some of my code. Maybe this is also interesting to others. https://github.com/acdh-oeaw/xqdoc I also found https://github.com/lcahlander/xqDoc-eXist-db mentioned on this mailing list. I plan to look into getting this to work on BaseX. Best regards Omar Siam

3 2

Options for ft:search
by Sebastian Zimmer 15 Mar '21

15 Mar '21

Hi, I'd like to request a feature concerning the ft:search method: An `lserror` option that works exactly like the global option `LSERROR`. It would be nice if we could set the maximum Levenshtein distance specifically for each fuzzy search without having to adjust the global option. Another question on ft:search: Is there a reason why it doesn't have a `case` option just like ft:contains has one? Best regards, Sebastian

2 3

Histogramming a large dataset
by Ron Katriel 10 Mar '21

10 Mar '21

Hi, I would appreciate your advice on optimizing a query against a large BaseX (9.2.4) database. It is loaded with data from the FDA’s Adverse Event Reporting System (FAERS). Currently this is just the 2020 dataset which comprises 12 documents stored as 308,870,597 nodes (6,565 MB). The queries below effectively - though not necessarily efficiently - implement a histogram. The first, which is applied to patient gender (sex), returns the results (3 items) in 52 seconds: 2 893694 1 583999 0 198 The second does this for patient weight - rounded to the closest 10 lbs increment. It takes 580 seconds to place the data into 67 bins. Initially I tried running it on the rounded weights but aborted the run as it was a taking an inordinate amount of time (there are 217 distinct weights in the dataset). Is there a way to improve the performance of this type of query? Thanks, Ron (: 3 items - 52 sec :) let $safetyreport := db:open('FAERS')/ichicsr/safetyreport for $value in distinct-values($safetyreport/patient/patientsex) return concat($value, " ", count(index-of($safetyreport/patient/patientsex, $value))) (: 67 items - 580 sec :) let $safetyreport := db:open('FAERS')/ichicsr/safetyreport for $value in distinct-values($safetyreport/patient/patientweight ! (. div 10.0) ! round(.) ! (. * 10)) return concat($value, " ", count(index-of($safetyreport/patient/patientweight ! (. div 10.0) ! round(.) ! (. * 10), $value))) -- The information in this email and any attachments are intended solely for the recipient(s) to whom it is addressed, and may be confidential and/or privileged. Any unauthorized distribution or copying of this transmittal or its attachments is prohibited. If you are not a named recipient or have received this email in error: (i) you should not read, disclose, or copy it, (ii) please notify the sender of your receipt by reply email and delete this email and all attachments.

3 6

Question about Staircase Join
by Yasir B 03 Mar '21

03 Mar '21

Hello, I am studying the paper "Storing and Querying Large XML Instances". [https://files.basex.org/publications/Gruen%20%5B2010%5D,%20Storing%20and%20…] This is very interesting and helpful to read! I apologize I fail to understand the following in 3.4.2.1 Staircase Join: "In the partitioned plane, the scanned areas are made disjunct, i.e., scanning is canceled whenever the pre value of the currently scanned node equals the pre value of the next context node." Since pre values are unique (?), I couldn't follow how the next context node would have the same pre value. For the partitioning step, I had the impression the next context node is not the same as the current context node, nor would it be a descendant of the current context node. Thank you, Yasir

2 1

map-entries sequence
by Rob Stapper 02 Mar '21

02 Mar '21

Hi Christian, In my casus I’m exporting and importing xQuery maps where the export-format is a xQuery-file or a json-file. Hereby the sequence of the exported map-entries is important: I want the sequence in which the entries are generated to stay in tact when exporting. I can’t get this working. My current work-around is to place the map-entries in an array. It does the trick but it feels redundant. Is there a way to have this kind of control over map-entry sequence? Thnx in advance, Rob Stapper Sent from Mail for Windows 10 -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

2 1

Write several XML files via one XQuery
by Brune, Nicole 01 Mar '21

01 Mar '21

Dear all, please excuse me if this has been covered in the documentation and I just haven't found it. I am trying to harvest some information from XML files in a database (all XML files) and create several new XML files with the information. I am aware of the function write:file(path, data). Is it possible to write several files in one go and via one XQuery? I have tried exchanging "../test.xml" with "../test[1 to 2000].xml, ..." but, unfortunately, it did not work. Thank you kindly in advance for your help! Best, Nicole

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk March 2021