Hi Holger, Thank you for your question. The two points you describe, would fit our use case precisely and make the script development a lot easier / faster.
Kind regards, Richard Van: [email protected] <[email protected]> Namens Holger Knublauch Verzonden: maandag 19 februari 2024 12:53 Aan: [email protected] Onderwerp: Re: [topbraid-users] Simple user interactions with Resource or Batch Actions Hi Richard, this is an interesting topic to me and we had similar use case, so please feel free to discuss this further. I believe there are two distinct topics here that could become their own development tickets: 1) A selection widget populated by arbitrary values, e.g. produced by a SPARQL query. This would allow you to write a SPARQL query or ADS script that fetches the SPARQL library queries. This COULD be implemented via a new DASH constraint type that returns an enumeration of valid values. 2) A way to have DASH actions that use multi-page wizards instead of just a single page with parameters. This may be implemented through ADS scripts that return some specific JSON, e.g. with something like { type: 'WizardPage', title: "Please enter your name", parameters: [ { name: "firstName", label: "first name", datatype: xsd.string, optional: false, } ... ], state: { ... }, callback: nextPage, } where a state object can be passed between pages to serve as implicit input to the ADS script of the next page and nextPage is some JS function that receives the state and the parameter values as name-value pairs. The dialog that drives an ADS action would then display a suitable "next" page when a script returns such a dedicated JSON. Does this sound about right? Holger On 16 Feb 2024, at 10:03 am, 'Richard Nagelmaeker' via TopBraid Suite Users <[email protected]<mailto:[email protected]>> wrote: Hi Holger, First I want to tell you, we will simplify the resource action. So it will generate all the information products at once and push them to Nexus. Next we will inform the user, the service products have been generated and stored by showing them a page with a link for each product. This is actually way easier to create and bypasses the issues I had questions about. Just so you know. To answer your questions, yes the SPARQL queries can change independently from the Modify Actions. The intermediate step is, for the end-user to decide which information product they will generate. Depending on the available data and requests from the organisation. But for now I will generate all information products for a specific dataset and look into the issue of product selection in due time. Maybe by then the selection is not needed anymore. About the focusNode, I wanted to use it since it's one of the available variables inside dash:js. Not because it's the "focusNode". The first thing I would do with the focusNode is point it to a resource in a separate graph where I keep track of the state inside the script. Thinking I could access the focusNode (since it's a supported variable inside dash:js) from within the users HTML front-end. But this would make it a really complex feature on your (EDG) side I guess. Anyway I won't use the focusNode for now. Thanks for the replies and support. Have a nice weekend, Cheers, Richard Op donderdag 15 februari 2024 om 14:19:38 UTC+1 schreef Holger Knublauch: On 14 Feb 2024, at 1:38 pm, 'Richard Nagelmaeker' via TopBraid Suite Users <[email protected]> wrote: Hi Holger, Yes correct, we want the user to select a query from the SPARQL Library. The user will do this by clicking a button or using a dropdown list, whatever is easiest to implement in an HTML Form, within EDG. The more technical and SPARQL savvy people, will build the queries and add them to the Library. >From a separation of concerns, ease of use and re-using what is already there, point of view. What we need is a way for the user to select the query and then for the script to generate an information product, based on this selection. This information product then needs to be stored within Nexus and / or send back to the user. We want to keep the interaction as simple as possible for the user, keep them away from the inherit complexity of EDG. Thanks for clarifying, Richard. So the SPARQL queries can change independently from the Modify Actions? Asking because it sounds like the alternative could be to store the queries as part of the dash:js of the actions. Why the additional intermediate step? I wondered if we could use the focusNode as a place to keep state, though this would require the user interaction to change the focusNode. I don't know if this is at all possible. Right, changing the data itself would be unusual, certainly for Explore operations. Holger Thank you for the support and the effort you put into it already. It is well received on this side. I hope this answer clarifies the requirements a bit. If you have any suggestions, I'm happy to receive them. Cheers, Richard Op woensdag 7 februari 2024 om 15:04:21 UTC+1 schreef Holger Knublauch: dash:Explore/Modify/BatchActions can take parameters that are declared using sh:parameter. The other input they receive is the focusNode, i.e. the currently selected resource. This means that the dash:js script may query the values that were entered/selected by the user for the parameters. There is, until now, no further way to open another page of parameters based on values entered in previous steps. I wish we had that capability, but it hasn't bubbled up to the top in priority. In your case, is my understanding correct that you want the user to be able to select a query from the SPARQL Library? Off the top of my head I cannot think of a way to do that from a sh:Parameter, although these offer the same features as other property shapes, including the ability to specify a dash:editor. But I think we lack a dash:editor widget that would be populated from a SPARQL query (or any other node expression). Maybe your use case would be addressed if we had such a widget. Would you mind clarifying your requirements a bit more based on this? Thanks, Holger On 7 Feb 2024, at 11:01 am, 'Richard Nagelmaeker' via TopBraid Suite Users <[email protected]<mailto:[email protected]>> wrote: Hi, Using EDG 7.8 is it possible to use Resource or Batch actions in combination with user interaction. The user interaction is needed, for the user to select the data product they want and receive the resulted product on their computer or even better, store the data product in Nexus. The data products are the result of a sparql query (stored in SPARQL Library) run on a reference data set. A dataset has multiple data products associated with it. We want the user to select what data product they want. Effectively the user selects the sparql query to generate the data product. For now we use an ADS Explore action. This uses a graph.select function to retrieve the list of queries (from the urn:x-evn-user-data). We could show this list to the user (using the graph.html function), but how can we receive the users response. The response is the selection of the specific data product (= sprawl query) by the user. Are the Resource (or Batch) actions able to receive user interaction? Or do you see another way around this, while still staying within EDG? For now we see an external user interface and an ADS API as a possible solution. But we prefer to keep things within EDG if possible. Regards, Richard -- The topics of this mailing list include TopBraid EDG and related technologies such as SHACL. To post to this group, send email to [email protected]<mailto:[email protected]> --- You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/f461bbb5-1c72-434a-94a8-6677c94f5cc5n%40googlegroups.com<https://groups.google.com/d/msgid/topbraid-users/f461bbb5-1c72-434a-94a8-6677c94f5cc5n%40googlegroups.com?utm_medium=email&utm_source=footer>. -- The topics of this mailing list include TopBraid EDG and related technologies such as SHACL. To post to this group, send email to [email protected] --- You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/ab318418-d1e6-464f-aa3e-de004fa0c220n%40googlegroups.com<https://groups.google.com/d/msgid/topbraid-users/ab318418-d1e6-464f-aa3e-de004fa0c220n%40googlegroups.com?utm_medium=email&utm_source=footer>. -- The topics of this mailing list include TopBraid EDG and related technologies such as SHACL. To post to this group, send email to [email protected]<mailto:[email protected]> --- You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/d9c69be5-d5ce-4a91-a086-7dbbeb476b82n%40googlegroups.com<https://groups.google.com/d/msgid/topbraid-users/d9c69be5-d5ce-4a91-a086-7dbbeb476b82n%40googlegroups.com?utm_medium=email&utm_source=footer>. -- The topics of this mailing list include TopBraid EDG and related technologies such as SHACL. To post to this group, send email to [email protected]<mailto:[email protected]> --- You received this message because you are subscribed to a topic in the Google Groups "TopBraid Suite Users" group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/topbraid-users/n21qxmI2H8U/unsubscribe. To unsubscribe from this group and all its topics, send an email to [email protected]<mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/5BA029DC-2893-45BE-8CF4-1B6B550840C1%40topquadrant.com<https://groups.google.com/d/msgid/topbraid-users/5BA029DC-2893-45BE-8CF4-1B6B550840C1%40topquadrant.com?utm_medium=email&utm_source=footer>. ------------------------- Disclaimer ---------------------------- De informatie verzonden met dit e-mailbericht (en bijlagen) is uitsluitend bestemd voor de geadresseerde(n) en zij die van de geadresseerde(n) toestemming kregen dit bericht te lezen. Kennisneming door anderen is niet toegestaan. De informatie in dit e-mailbericht (en bijlagen) kan vertrouwelijk van aard zijn en binnen het bereik van een geheimhoudingsplicht en/of een verschoningsrecht vallen. Indien dit e-mailbericht niet voor u bestemd is, wordt u verzocht de afzender daarover onmiddellijk te informeren en het e-mailbericht (en bijlagen) te vernietigen. Conform het beveiligingsbeleid van de Politie wordt e-mail van en naar de politie gecontroleerd op virussen, spam en phishing en moet deze e-mail voldoen aan de voor de overheid verplichte mailbeveiligingsstandaarden die zijn vastgesteld door het Forum Standaardisatie. Mail die niet voldoet aan het beveiligingsbeleid kan worden geblokkeerd waardoor deze de geadresseerde niet bereikt. De geadresseerde wordt hiervan niet in kennis gesteld. --------------------------------------------------------------------- The information sent in this E-mail message (including any attachments) is exclusively intended for the individual(s) to whom it is addressed and for the individual(s) who has/have had permission from the recipient(s) to read this message. Access by others is not permitted. The information in this E-mail message (including any attachments) may be of a confidential nature and may form part of the duty of confidentiality and/or the right of non-disclosure. If you have received this E-mail message in error, please notify the sender without delay and delete the E-mail message (including any attachments). In conformity with the security policy of the Police, E-mails from and to the Police are checked for viruses, spam and phishing and this E-mail must meet the standards of the government-imposed E-mail security as set by the Standardization Forum. Any E-mail failing to meet said security policy may be blocked as a result of which it will not reach the intended recipient. The recipient concerned will not be notified. --------------------------------------------------------------------- -- The topics of this mailing list include TopBraid EDG and related technologies such as SHACL. To post to this group, send email to [email protected] --- You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/c9bcc741f1c64c1cb06f0c9f1d248954%40politie.nl.
