Seedea, scalable creativity
Xye, consultancy for serious creators
Seedea : leveraging EE on your cognitive swarm
Associate APIs to a specific usage within Seedea, the focus is to foster those new automated tool in order to favorably allow innovation and creativity (NOT to use yet another new trendy API).
wiki-based (content to work on and mechanisms themselves) MAS
Services should help to work on CAEE :
|specificity||AWS sip||statistically improbably phrase|
|authorship||pmwiki||stats on updates|
|core highlighter||find and highlight the invariant of an idea by?||SIP that stays over time|
|new software tools||internal||Yahoo!Pipe to aggregate (freshmeat,sourceforge and gitweb) and filter(on keywords) or used specialized reps( http://www.projet-plume.org/ ), see also Wakoopa|
|re-caller||display and discard or keep pieces of information of a list page||based on tools and memorization research (forgetting curve and autobiographical memory)|
|selector||display and discard or keep pieces of information of a list page||based on tools and investing research (like market-based products)|
auto-adjusting based on user response (as discussed clearly in DI05)
use the phylogenic view restricted to creativity
to find the key tools to transform to bot/services in the correct order (based on similar pattern!) for faster engineering have better acceptance
make the word cloud microservice subscribed by default to utopiah (and unsubscribable only by him thus asking identification when "x" by someone)
signal the wiki that we start handling it (start the visual spider animation, clikable to have details on the "ongoing work") handle the idea content ("per idea" or "per idea per user"?) save in Oimp-nodeas.nodeafunc-oimpname-uniqmicroservicename-nodeomicroserviceversion (thus having a compatible history of updates too, should enable to see an evolution over time) check the notification method and use it log whatever is required wherever it is required signal the wiki that we finished handling it
then produce a generic template to repeat it for other APIs
Using a personal notation like "nodea" (proposed during the early research period) or "microservices" could give more uniqueness but could also be confusing at the same time ("yet another term").
|Suggestion engines||cf dedicated section in the creativity article||Specialized engines should be based on the category detected (cf following service)|
|Correct vocabulary||?||Very basic but still useful especially for professional presentation.|
|Abbreviation||abbreviations.com||Facilitate micro-blogging/SMS conversion|
|Name||Name Masher||Does not seem to provide an API so far!|
|Category||uClassify||Suggest one or many categories amongst : technology, science, philosophy, art, ...|
|Word cloud||?||Having a quick view of the content of the page.|
|Link share||AddThis||Being able to share interesting ideas with others quickly.|
|Literacy review||?||Check the length of the sentences and infer on the expected public.|
|Non-Seedea microservices tracking||Wakoopa||Being able to track tools but based on local running softwares, not internal or external services.|
|Structuring methodology||Presence of keywords and length of their associated sections.||Check if the user added key structuring elements (title, keyword, visual, references, etc).|
|Activity methodology||Long-term statistics of usage and suggestion based on patterns of successes and failures.||Used to keep the user focused on his task.|
|Opportunity time slice detector||Probability of lowest edit moment based on activity statistics.||Used to make suggestions without disturbing the user.|
|Concept tracking||(CAEE based) Exploiting bibliographic data to track back the origin of the key component of the idea||Providing a visual but also suggestions (see how other fields previously helped the discipline progress, Suggest similar paper, ...)|
|Services suggestion||(CAEE based) See what user with similar method or interested liked recently (Ev. Epistemic Actions?).||Evolve the network of services based on personal usage.|
|Services weather||check periodically the status of each service (and compare it to the overall situation||Freq X or with event Y : try <test-value,expected-result> then do A or B. Also store the response time, compute its average and its evolution over time (to predict degrading performances and provide a potential alternative solution).|
|CAEE methodology||Combining the previous services to maximize efficiency.||Our core real core added value : methodology (EE) supported by tools (AI netMAS)|
In general see WikiBot regarding internal mechanisms.
Introduce microservices (bots/nodeas/affordances/epistemic actions) gradually to users based on results from CAEE.
Simulating the Ontogenic View (OV) based on Phylogenic View (PV) studied. Eventually Mixed View (MV) can be used to initialize a user account (using another user as a model).
This chronological approach should facilitate adoptions of microservices more efficiently.