Closed mmisw closed 7 years ago
From jbgrayb...@mindspring.com on August 22, 2014 12:04:58
Owner: ---
From caru...@gmail.com on August 22, 2014 12:09:52
Not yet documented and still work in progress but the generic engine that enables CFSN is being refactored here: https://github.com/mmisw/scv (I likely will be renaming this to vocbrowser, or vrowser, or ...). Besides facilitating the customization of the browser to a particular vocabulary (like in cfsn) but end users, the idea is to also automatically dispatch vocabularies at the ORR with the new interface.
From caru...@gmail.com on August 22, 2014 13:40:03
Mentioned repo just renamed to https://github.com/mmisw/vrowser Some experimental deployments:
From caru...@gmail.com on October 07, 2014 20:50:24
just to note that the mentioned repo was later on renamed to https://github.com/mmisw/vbrowser And the experimental deployments:
From caru...@gmail.com on October 07, 2014 22:57:32
That last one should be
From jbgrayb...@mindspring.com on August 22, 2014 11:52:59
What capability do you want added or improved? I want to improve the display of terms in ORR (see also issue #326 ), particularly values shown within the table. First priority is to provide auto-recognition of things that can be linked: A) Link back to the parent ontology B) URLs within the parent ontology auto-linked C) URLs elsewhere auto-linked (different color) D) Codes or Terms that are within the parent ontology auto-linked, to resolve on the appropriate ORR term page (see other details below)
Second priority is to add known mappings, as CFSN does. Where do you want this capability to be accessible? Each term page What sort of input/command mechanism do you want? What is the desired output (content, format, location)? Following CFSN format Other details of your desired capability? Later it would be cool to do CFSN's _ term recognition for searching, but recognizing more types of terms:
Original issue: http://code.google.com/p/mmisw/issues/detail?id=327