Date: prev next · Thread: first prev next last
2021 Archives by date, by thread · List index


Hello all,

the next design/UX meeting is on Wednesday, Apr/07,
20:00 Berlin/CEST/GMT+2 resp. 6pm UTC.


Plan is to discuss the Data Provider GSoC project, as asked for on the mailing list. Tushar (or Vikas?) prepared a page at https://wiki.documentfoundation.org/User:Tusharrai2017, and we have an enlightening chat. My summary:


Data Provider should become
* https://wiki.documentfoundation.org/Development/GSoC/Ideas#Implement_interface_for_external_data_source_import_into_Calc "With more and more data in different forms it becomes more and more challenging to visualize and evaluate them. Calc could be an amazing tool to allow inspecting existing data. To allow that we would need an interface to import and more importantly update data from external data sources. The interface should be modelled similar to how the orcus interface is currently implemented and the data should be stored inside of a ScDBData (a database range). The interface would then be used together with either an existing document where you mark a range for the external data or a template document that is automatically filled."

Previous work
* is supposed to work https://ask.libreoffice.org/en/question/241778/how-is-data-provider-supposed-to-work/
  + existing interface can be customized into the UI (search for Data Provider)
    but is not functional
* code https://github.com/LibreOffice/core/tree/master/sc/source/ui/dataprovider
* open tickets https://bugs.documentfoundation.org/show_bug.cgi?id=120219

Data are
a) file-based such as ODS, CSV, HTML/XML etc. loaded via File > Open... with the Text Import dialog to define separators and the final column type b1) stream values loaded via Sheet > Link to External Data.. (eg. https://coinmarketcap.com/) with option to update
b2) stream values loaded via Data > Streams... (does not work for me)
c) XML structure per Data > XML Source with option to pick source node and target range

To be done

* Requirements (unclear since "visualize and evaluate / inspect data" is
  not "import / store" and "transform")
  + Eve wants to _inspect_ the content of a huge CSV file before loading
    to pick the right file.
  + Eve wants to _transform_ the values of a data stream to convert
    imperial Fahrenheit to metric Celsius.
  + ...
* How to integrate
  + Option 1: as another dialog, eg. Data > Data Provider...
  + Option 2: optionally with existing procedures,
    eg. [Help] [Transform] [Ok] [Cancel] or per checkbox "[ ] Transformation"
    that present user with a dialog
* Complexity of transformation
+ http://gettingstartedwithlibreoffice.blogspot.com/2018/08/added-data-tranformations.html seems pretty basic and wont cover F to C conversion
    (<F> - 32 * 5/9 = <C>), for example



Hope to see you on Jitsi at https://jitsi.documentfoundation.org/design

Cheers,
Heiko

--
Dr. Heiko Tietze, UX-Designer and UX-Mentor
Tel: +49 30 5557992-63 | Mail: heiko.tietze@documentfoundation.org
The Document Foundation, Kurfürstendamm 188, 10707 Berlin, DE
Gemeinnützige rechtsfähige Stiftung des bürgerlichen Rechts
Legal details: https://www.documentfoundation.org/imprint


--
To unsubscribe e-mail to: design+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/design/
Privacy Policy: https://www.documentfoundation.org/privacy

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.