|↑back Search ←Prev date Next date→ Show only urls||(Click on time to select a line by its url)|
|***||gac410 has left||[04:11]|
|..................... (idle for 1h41mn)|
How to fix Software erron in FosWiki??
|.............. (idle for 1h6mn)|
|***||ChanServ sets mode: +o MichaelDaum
foswiki_irc0 has left
|OliverSchaub||@MichaelDaum: Good morning... we just upgraded to the latest SolrPlugin. Search and Indexing seems to work fine. (one strange indexing-bug... I will open a Task for it). But there is also a small Bug on the Search-Page itself... the URLPARAM "search" is set as the value of the Input-field, but is ignored on initial search. Also, the value (even there in the DOM) is not displayed in the input-field itself.
I typed in manually after loading the page, search works as expected...
I = If
|MichaelDaum||yes the URLPARAM in the template is pointless
note that the format of the query string to the solr search doesn't use url params anymore
as it is all ajax now, the thing manipulates the anchor as required
|OliverSchaub||Aha... so how would an inital-call to the search page look like?||[07:15]|
|OliverSchaub||Ahhhh... I see. Yep, this is working. We'll change our Search-Forms accordingly.... Thanks for your quick Help.||[07:22]|
|MichaelDaum||OliverSchaub, use this http://trac.foswiki.org/browser/trunk/NatSkin/templates/searchbox.nat.tmpl and this http://trac.foswiki.org/browser/trunk/SolrPlugin/pub/System/SolrPlugin/solr-searchbox.uncompressed.js to create the search box||[07:30]|
|FoswikiBot||[ solr-searchbox.uncompressed.js in trunk/SolrPlugin/pub/System/SolrPlugin – Foswiki ]||[07:30]|
|***||ChanServ sets mode: +o CDot||[07:40]|
|.......................................... (idle for 3h28mn)|
I've got a question regarding DBRECURSE. So this is probably best answered by MichaelDaum, I guess...
|@MichaelDaum: For a scientific sample database I'd like to expand a parent-child like relationship, that (for usability reasons) is based on a 'Parent' formfield rather than a META-data based approach. So each sample topic lists its parent sample (if present) in the 'Parent' formfield. I understood that this relationship should be resolvable using DBRECURSE, but so far, I failed implementing it...||[11:19]|
|MichaelDaum||PhilippLeufke, have a look at ClassificationPlugin which gives you this kind of hierarchical data structure as Category formfields
there are isa() and subsumes() predicates added to the DBQUERY language then
as well as distance()
to query properties of the hierarchy and its nodes
technically, parent-child relation is cached in a distance matrix, which is more efficient than a recursive query.
does that make sense 4u?
|PhilippLeufke||Thanks for the very quick reply! I'll have a look, as I don't use ClassificationPlugin yet...||[11:24]|
|MichaelDaum||thats what this channel is for :)||[11:26]|
|PhilippLeufke||Let me shortly describe what I'm trying to implement: Using a view template (or in a summary table of all samples), the whole pedigree of a sample should be displayed, possibly with the current state (topic name / sample ID) highlighted. E.g., when viewing sample004's topic: sample001 > sample003 > *sample004* > sample006. Of course, each sample topic only features the sampleID of its direct parent in the '"Parent' formfield.||[11:30]|
ClassificationPlugin comes with a %CATINFO macro which lets you display the properties of a topic
|PhilippLeufke||However, the user would have to classify the sample separately, right?
I mean, filling out the 'Parent' formfield with 'Sample004' won't suffice then, right?
Where can I find documentation about CATINFO?
each sample has got its own parent property thus forming all of the pedigree
I just noticed that CATINFO and TAGINFO aren't properly documented in ClassificationPlugin
|PhilippLeufke||But will CATINFO on Sample001 still show the _whole_ pedigree then?||[11:42]|
|MichaelDaum||anyway, the plugin will be able to maintain foswiki's native parent property based on the categorization info automatically. so the breadcrumbs navigation will reflect the inheritance automatically.
it displays info about its own classification
it can also display the list of direct children
|PhilippLeufke||Hmm, I think, I'll be better off using META("parent") and CALC in order to find the topmost parent and then perform a DBRECURSE on this one. Of course, then the the samples pedigree must be represented by the topic structure and the desired 'Parent' formfield would be useless...
Maybe the reversed lookup of DBRECURSE, as discussed before in http://foswiki.org/Support/Question641 , would be helpful here as well.
|MichaelDaum||thats not going to be efficient
for a sample on level 6 it would mean 6 queries over all topics in your web
for a simple view ofthe topic
|PhilippLeufke||Due to the DBRECURSE query?||[11:59]|
every recursive step means: perform the proceeding step by searching it in your data
hop there. then do the same again.
this info is already cached in classification plugin internally
so there's no need for recursive searches
|PhilippLeufke||I see. Then this makes especially sense when creating the summary tables, where many samples are going to be processed.||[12:02]|
|MichaelDaum||also: category plugin lets you model samples with multiple parents
as well as one sample taking part on two or more ontologies
each with its parent-child hierarchy
|PhilippLeufke||But, I understand, the topic hierarchy has to reflect the sample pedigree, then, right? Or do you see any possible solution using the 'Parent' formfield that I initially intended?||[12:03]|
|MichaelDaum||the plugin comes with a new formfield type.
your current Parent formfield presumably is a plain text field
the new formfield type would be 'cat' instead of 'text'
|PhilippLeufke||Ah, I see. Can this be rendered as a 'select' field which allows the user to choose the parent from a DBQUERY-generated list of all samples?||[12:07]|
|MichaelDaum||it renders as a treeview of the ontology which lets you select the ancestors
similar to this: https://demo.michaeldaumconsulting.com/Knowledge/CategoryBrowser
|PhilippLeufke||Nice. where can I get inspired regarding source code using the ClassificationPlugin? Any sandbox web somewhere maybe?||[12:13]|
|MichaelDaum||have a look at this demo site
are you from Karlsruhe?
|MichaelDaum||ah kool. 1&1 are using this stuff as well. been onsite there last year for a couple of weeks.||[12:15]|
|PhilippLeufke||I noticed that Testo is/was one of your customers. Small but nice company from my hometown :-)||[12:17]|
they are still one of my customers. all of their intranet is based on classification plugin and whatever.
pretty hard to visit them down in Lenzkirch ;)
|PhilippLeufke||You should have stayed for holidays. Beautiful...
Anyway, thanks for your valuable tips. I'll try them out and see where I end up. Have a nice day!
|***||ChanServ sets mode: +o gac410||[12:35]|
|GithubBot||[foswiki] FoswikiBot pushed 1 new commit to master: http://git.io/64DrLg
foswiki/master 70b7b18 MichaelDaum: Item12576: improved javscript click behavior editing chapters; fixed html markup displayed un-rendered in the modal dialog's title bar...
|***||GithubBot has left||[12:42]|
|FoswikiBot||http://foswiki.org/Tasks/Item12576 [ Item12576: clean up title of modal dialog ]||[12:42]|
|..... (idle for 23mn)|
|***||PhilippLeufke has left||[13:05]|
|........... (idle for 53mn)|
|ChanServ sets mode: +o Lynnwood||[13:58]|
|FloPri||We are using the commentplugin. is there a way or an idea how i can store old comments. i am thinking of a simple button and when i click it the comment is transfered to another topic where the old comments are stored. any ideas how i can do this?||[14:10]|
|gac410||hm... how about put all comments into a separate comment page including the latest, and use a %SEARCH or %INCLUDE with pattern to see the most recent. The Extensions/WebHome does that for news items.||[14:15]|
|MichaelDaum||FloPri, how about using MetaCommentPlugin and limit the number of comments displayed?||[14:17]|
|gac410||Ah... Micha. Did you see my change to the news page - The set statement you added broke the include pattern on WebHome. I moved it to meta settings.||[14:18]|
I'v been adding an rss feed for the ExtensionNews
|gac410||I'm not sure if it was the bullet itself, or the @#$*(& html comments. ... cool||[14:19]|
|MichaelDaum||twas the bullet||[14:19]|
|MichaelDaum||here's the timeline of things foswiki found on the net, including the extension news rss feed: http://www.dipity.com/nuddlegg/Foswiki/||[14:19]|
we need to crank up activity on foswiki again for 1.1.9 and 1.2/2.0 Though not today :( Moving a front loader washer up a flight of stairs ... somehow ...
|jast||urg, those things are a pain to lift||[14:24]|
|MichaelDaum||I would lend you a hand ... just to get you back on the foswiki train quicker ;)||[14:24]|
|jast||though I've found it depends on the model||[14:24]|
|......... (idle for 40mn)|
|FloPri||MichaelDaum: thx i will give it a look||[15:04]|
|***||sneex has left||[15:04]|
|.................. (idle for 1h28mn)|
|PhilippLeufke||@MichaelDaum: still there?||[16:32]|
|MichaelDaum||hey there. almost. preparing backups to finish the day.||[16:32]|
|PhilippLeufke||I installed Classification plugin but I'm having trouble to actually understand it with the given documentation.
I tried the 'cat' type in the data form, but as no categories are defined yet, there is nothing to choose from, I guess.
Is there a way to _automatically_ register every sample as a category of its own? And where do I manually create categories? I discovered the Applications.ClassificationApp web, but honestly, I'm pretty clueless there.
Uh, but if my questions are not compatible with your "Feierabend", it's perfectly fine if you could help me tackle the problem tomorrow...
|MichaelDaum||as soon as your samples have a formfield TopicType=Category and a Category formfield to point to its own parent, the thing qualifies as a category
and will be displayed in the tree view
we can continue on it tomorrow ;)
|PhilippLeufke||Thanks, I'll try that. Have a nice evening...||[16:40]|
|↑back Search ←Prev date Next date→ Show only urls||(Click on time to select a line by its url)|