thanks holger I guess I'm looking for a future-proof pattern for those wrappers so I can write my own using the same libraries and coding styles. :-)
I have been looking at the ui.ttlx as normal - they dont give a lot of useful examples for the parameters though and its experimentation sometimes to work out what form things are in sometimes and the hidden assumptions about import closures. _______________________________________________________ kind regards *Rob Atkinson* Lead Ontologist, Knowledge Architect at SURROUND Australia Pty Ltd Address Level 9, Nishi Building, 2 Phillip Law Street; New Acton Canberra Australia 2601 Phone + <http://++61+466+491+056/>61 419 202 973 Email [email protected] https://www.surroundaustralia.com *Enhancing Intelligence Within Organisations* *delivering evidence that connects decisions to outcomes* *Copyrights:* SURROUND Australia Pty Ltd is the copyright owner of all original content and attachments. All rights reserved. *Confidentiality Notice:* The contents of this e-mail are confidential to the ordinary user of the e-mail address to which it is addressed, and may also be privileged. If you are not the addressee of this e-mail, you may not copy, forward, disclose, or otherwise use it or any part of it or its attachments in any form whatsoever. If you have received this e-mail in error, please e-mail the sender by replying to this message. On Tue, 3 May 2022 at 10:04, Holger Knublauch <[email protected]> wrote: > > On 2022-05-03 9:52 am, Rob Atkinson wrote: > > Thanks Holger > > I'm still on 7.1 for now - though after project initial build will have > option to upgrade to 7.2 :-( > > for the "supported in 7.2" API > > I guess my best guess would be to create a proxy function to mirror this > 7.2 function. > > tbs.createAssetCollection > > is there a way to get access to details without a 7.2 install? > > Essentially it's a wrapper around the SWP element teamwork:createProject > with a bit of syntactic sugar. You can see that in use when you look at the > network traffic when you manually create an asset collection. > > > and for general service invocation... > > looking for documentation on these i can find graph.swp in the scriptAPI > > but I need then to dive further into > > > @param {?object} [params] - name-value pairs for the arguments of the > element, typically as GraphNodes > > so I went looking for the Teamwork functions reference - I notice a lot of > the different doc entry points have been cleaned up (a Good Thing) so I'll > start with a quick question as to where I would find such documentation now? > > The most comprehensive documentation for SWP elements is to just open them > in the editor, i.e. with TopBraid EDG Studio just open teamwork.ui.ttlx and > you'll see > > So it would be something like > > graph.swp('teamwork:PublishProjectToNamedExplorer', { projectGraph: > 'urn:x-evn-master:mygraph', userName: 'robXY', ... }) > > The ui:prototype above may answer your other questions. > > Holger > > > > in this case teamwork:PublishProjectToNamedExplorer > > - so how does this relate to > https://sop.dev.bdr.gov.au/edg/tbl/sendProjects - which seems to > be tbladmin.sendProjects() - i guess a function in the react bundle that > does something under the hood to invoke that service? I that function > itself based on a generic service call we could use without raw jquery ? > > > > /** > * Runs an SWP element with a provided set of parameters. > > * This can not be used in read-only mode and should be used by > experienced TopBraid users only. > * > > * NOTE: This function is likely going to be deleted in future versions. > Instead users are encouraged to explicitly > > * mark the SWP scripts that they want to call, using > ui:scriptFunctionReadOnly and then use the generated functions. > * Meanwhile this function here is kept to simplify experiments. > * > > * @param {string} viewClass - the qname of the view class in the > ui:graph, e.g. 'ex:MyElement' > > * @param {?object} [params] - name-value pairs for the arguments of the > element, typically as GraphNodes > * @returns {string} the SWP response as a string > */ > swp(viewClass, params) { > return __jenaData.swp(viewClass, params); > }, > > On Monday, May 2, 2022 at 6:49:23 PM UTC+10 [email protected] wrote: > >> >> On 2022-05-02 5:13 pm, Holger Knublauch wrote: >> >> Hi Rob, >> >> assuming you're on 7.2, ADS now supports a new API that includes >> functions like tbs.createAssetCollection which you could theoretically use >> to create a clone which you later tbs.deleteAssetCollection(). >> >> On 2022-05-02 3:22 pm, Rob Atkinson wrote: >> >> >> hi >> >> havent been able to find in the docs or examples, but suspect I may be >> missing something. >> >> I have a DataGraph I want to publish to two different explorer instances >> - but with different data in each. Some other things may happen - custom >> review steps - so its going to be in ADS. >> >> So I need an ADS script capable of (say) cloning and modifying an asset >> collection then pushing the two graphs to two different Explorer >> instances. Looking at the calls the endpoint and username is picked up >> from the server config - for a default location. >> >> How should one invoke such services in ADS - is it a matter of building >> up my own utility library on top of jquery or does something else exist? >> >> >> Publishing to Explorer is not part of that API (yet). ADS can make >> generic web API calls using IO.http() in case you want to simulate the >> network traffic that you see, e.g. to invoke the sendProjects service by >> hand. That's not an elegant solution, but from what I see a necessary hack >> for now. I am not 100% up to date on the web services but will follow-up >> here if my colleagues have a better idea. >> >> Maybe try graph.swp('teamwork:PublishProjectToNamedExplorer', { ... }) >> >> HTH >> Holger >> >> >> >> >> Is there any advice re respecting permissions of the user, or allowing >> the script to do something i dont want the user to do normally ? >> >> ADS scripts cannot switch users, so you'd need to invoke this from a user >> with sufficient permissions. >> >> Holger >> >> >> >> Cheers >> Rob >> >> >> >> -- >> 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/1a94dfe9-4d1b-4ed6-946d-75adc72e2ed7n%40googlegroups.com >> <https://groups.google.com/d/msgid/topbraid-users/1a94dfe9-4d1b-4ed6-946d-75adc72e2ed7n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> -- > 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/7d43627f-1b6b-403b-8aef-5a3ada815d57n%40googlegroups.com > <https://groups.google.com/d/msgid/topbraid-users/7d43627f-1b6b-403b-8aef-5a3ada815d57n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > -- > 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/7Lla6sBnK28/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/topbraid-users/ce16892d-622a-d192-b8f1-695042de6e80%40topquadrant.com > <https://groups.google.com/d/msgid/topbraid-users/ce16892d-622a-d192-b8f1-695042de6e80%40topquadrant.com?utm_medium=email&utm_source=footer> > . > -- 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/CAOBWeKu_qeCQofGCZiNRLJtU_1Q_dTuC9yCfOSLY%2B4_GkUJPDA%40mail.gmail.com.
