dhiraj
Nov 10, 2009 06:36 PM
Tell us your Use Cases!
We would love to hear what you are using Cyn.in for.
Particularly:
1. What's your use case? Cyn.in can be used in several different ways, and we love to hear feedback. Constantly listening helps us help you by improving the product with every iteration.
2. What features / functionality / parts do you *really* like? What would you like to see more of, or where do you think we should go deeper?
We would love to hear what you are using Cyn.in for.
Particularly:
1. What's your use case? Cyn.in can be used in several different ways, and we love to hear feedback. Constantly listening helps us help you by improving the product with every iteration.
2. What features / functionality / parts do you *really* like? What would you like to see more of, or where do you think we should go deeper?

Blog
Status Log
Wiki
The Community here has been so responsive (there are some unaswered questions out there yet), but my plan is to migrate to 3.05 and migrate content from other sites to this place to make this interaction more plublic/open. Localization & plugins or custom dev is in the near/middle term future.
Yes, this idea is also being explored by a few other people as well - bridging multiple institutions and community, together - so you're definitely not alone in this. It's an excellent idea, do let us know how it goes.
Regarding localization - translation is possible, we're working on Spanish translation, this should become available soon.
* To be able to put Video & Audio resources as external references (not only uploaded to the cyn.in site) and also to have the Kupu editor accessing this multimedia resources more easily.
* Blog post should have the description and other metadata upper in a column, so people could decide is if worth to read easily.
* Short permalinks (like tinyurl or ur1.ca) would be nice and
* if you see your first post, someone edited it and ask about the rights systems. In discussions, the original post should be only editable by the original poster by default and only available for edition by selected people.
Short permalinks -> Yes, the URL story needs an update for discussions and status messages. Will do soon.
Discussions -> We're already looking into fixing the Edit behavior -> http://odn.cynapse.com/issues/1168
Playable SWFs: This is actually the *third* aspect of embeddable flash that Cyn.in could benefit with, the first being directly playable video (FLV,MP4) which we already do, and the second being embeddable 3rd party players (youtube, et al). For each of the three aspects a different type of "Player" is required. In the first type, we have an internal player that will play compatible video files uploaded to Cyn.in. To have 3rd party embeddable video, we'd actually have to switch the player based on detected service - so for YouTube we'd use the YouTube player embed API, for MetaCafe something else, for each service a different strategy must be adopted. For directly playable SWFs, we'd probably need to create a 5th File based type (existing 4 are File, Image, Audio and Video), that would be called something like an "SWF Animation" and would perhaps even allow Creators to input desired width and height that they want to show it off in. Do note however that while this has immense benefit in things like Computer Based Training and Screencasts with interactive navigation and so on, this does also open up a whole new can of worms - Flash games. I fear that some of the Enterprise customers would be a bit apprehensive about this feature - it would make it too easy (almost like an invite) for users to upload games and other kinds of media that would detract from the whole experience by causing wasting of their users' precious time. Again, this is me hypothesizing a problem which possibly wouldn't happen at all - we're all responsible people with clear, open consciences here, right? :)
But these *are* the kind of decisions we are forced to take. Often.
There *does exist* a way that you can utilize SWF content directly in the current Cyn.in version - by using a Rich HTML container to host it - albeit with some required understanding of Flash Object embedding with OBJECT and EMBED tags. You upload the .SWF file as a regular plain old File first, and then open up a new Wiki Page or Blog post and use the External link (green globe) button in the WYSIWYG editor to paste the object tag into the Embed tab that is present. If you're using a tool to create the SWFs, then probably the same tool will also be generating a companion HTML file for the SWF, open it up, look for the OBJECT tag in it, copy paste it into a regular text editor so that you can change the SWF file url. Typically the HTML file will be referring to the SWF file without a path, you have to use the full URL to the SWF file that Cyn.in will show you once you upload it.
Tip 1: Remember to strip of the /view at the end of the file URL when you're pasting it into the object tag
Tip 2: There will typically always be 2 places to paste the SWF URL, one in the OBJECT tag, and one in the nested EMBED tag.
Screencasts: You know, they actually take way lesser time to initially draft, but then the post-processing that is manually required to be done gobbles up so much time it's literally astounding the amount of effort and time you realize you put in to making that 10 minute video, by the time you're done with the editing and tweaking and transitions and audio voiceover and so on. So (at least IMO) it's really easy to do a mediocre video that will at maximum give a rough understanding, moderately difficult to do a screencast that will successfully explain all the things that you wanted to, and the truly well done video that will keep *all* of the audience 100% engaged throughout the viewing, while at the same time getting all your points across is ...... impossible? :)
Plus, there are additional problems with doing *only* screencasts as documentation (a side effect of what happens when you spend that much time making the video perfect) - a lot of people, especially in the enterprise sector are not really comfortable with the Cyn.in solution without having the written and diagrammatic documentation filed and ready, in any case! The reasoning is this - written documentation can be incorporated into a process driven approach easily. So personnel can be given a printed manual that can be studied to know how to use the system. And there are many other compelling arguments for written documentation along similar lines of thought. Like it's easier to visually scroll / skim through the parts of written documentation while in a video it's always seek, see, seek back, see, seek forward, and so on.
All that said (I did ramble on a *lot* on this one, all apologies) screencasts *are* cool and can have the maximum impact when done properly. I do wish we did more of them too. ;-)
Any guidelines for integrating the Help Center? I really like the features it offers but have had a very difficult time getting it integrated.
* In discussions, the original post should be only editable by the original poster by default and only available for edition by selected people. - Hmm you are right about that, the edit allowed to everyone makes sense for Wiki pages but not for discussions. We need to design custom workflows for the discussion content type, and maybe even blog posts?
i can now add screenshots and doc's not forgeting the scripts themselves for download, users can ask questions, comment, maon.
Well done guys
Would love to *see* it though. Is the site publicly available yet? Please share the link if you can, thanks.
1) Their privat workspace... department related documentation
2) Workspace that other departments may read, but not add content, for documentation that should be shared between departments, but maintained by one department only
3) Workspace that all loged in users can read, but only that department can contribute.
We will also have a common firm section, with overall info for workers, and we are gona setup a small "Playground" space for photo albums, our video and audio works, and so on....
The fact of "Contributor published" and "Viewers published" abillaty helps us alot in our scenario. But for some stuff there should be more accassible information / help... like Advanced Collections... How? What?
And... you found the Advanced Collections portal type. That one was originally for internal use only - it's a direct portal_catalog query, you have to pass a python dict of query parameters and if you know what you're doing, you'll get results straight from the catalog.
I found an option that I didn't know what does it do :D ... And it's not like it wasn't out there straight in the open :)
We had this implemented in one of our custom made previous systems. While interlinking wikis is a great idea, nesting of them is also a fantastic feature. Mabey 1 or 2 levels deep nesting. So for acutaly wikis that have a same part, and should change in all wikis if changed in one, you only update a nested wiki...
Just an idea :)
We would create a header wiki and a footer wiki for several documents... The wikis that needed this headers and footers would have a text in edit mode like:
"[wiki:header_wiki]
SOME WIKI TEXT
[wiki:footer_wiki]"
And when that wiki was viewed it head somehing like:
" TEXT FROM A WIKI header_wiki
SOME WIKI TEXT
TEXT FROM A WIKI footer_wiki"
so, several documents using this headers and footers could be changed at the same time simply by editing only 2 wikis...
I hope this makes it clear :)
You have my +1. Which also means it gets added as a feature request wish in ODN. ;)
Here, tell me what you think: http://odn.cynapse.com/issues/1194
You are tieing wikis to space insted to other wikis... what I mentioned was mabey a bad sample...
Consider this 2 wikis then:
"[wiki:INSERT_WIKI_1]
[wiki:INSERT_WIKI_2]
SOME REGULAR WIKI TEXT
[wiki:INSERT_WIKI_3]
"
" A REGULAR WIKI TEXT FOR THIS WIKI
[wiki:INSERT_WIKI_3]
[wiki:INSERT_WIKI_1]
[wiki:INSERT_WIKI_2]
SOME MORE REGULAR WIKI TEXT"
get my point? :D
Will look into this soon, hopefully.
This is possible with simple modification of UI templates, there's no configuration UI for changing these, at present. So you're basically looking at not having identity disclosure? What about avatar photos? Or is that okay?
Yes, well we did consciously take that decision to show the full name of the person where it made sense. It usually fits decently in the closed group collaboration area that a large portion of Cyn.in's audience lies in.
Good point though, perhaps we should offer such an option as well, to hide identification revealing details of users. Will try to get this looked into, in the (hopefully) near future.
1. Collaborative Document Editing (Adobe Acrobat or Wikis?) for research bid writing, documentation
2. Project workgroup (private wiki, some blogging, file sharing, forums)
3. Departmental Showcase ( public blogging, some wiki stuff all with design polish) <-- it's a shame cyn.in is weak here with no "open access/no login required" spaces. Perhaps this can be achieved by "presenting" an RSS feed from a space somewhere else...
... all with added social media "fluff" and increased people discoverability
So far we've trialled (quite extensively) SocialText (commercial), LifeRay, Jive (commercial) Confluence, Elgg... and looked at many, many others including omCollab (a blend of WordPress, MediaWiki, phpBB etc) and fosWiki...
For some reason, I hadn't come across cyn.in... so far it looks FANTASTIC!!!!!
Most PHP / curl based CMSes (and many other) systems will work with the URLed authentication way above, and you can directly consume+aggregate+publish. Files, Images, Audio and Video are available as enclosure items in the feeds. It's safe enough for server to server communication, and besides, the idea is that you dedicate a separate "public user" that can only see that Space and all the content that you want to pull is on that Space. Drupal's feed modules, for example, are particularly potent when you look at re-purposing them this way.
What i could offer is a proper german localization ... the demo doesn't look very well translatet and does not support ä ö ü.
We have 75 users on the system right now and each has a private (not visible to other users) space and I've taken all the files each user has on their work-stations and have migrated them into Cyn.in where they are now quickly searchable from the desktop client. My philosophy with this move is that I can now just backup the Cyn.in virtual appliance instead of 75 work-stations, relieving a huge IT burden.
Cyn.in has really excelled at using it for our extensive training videos which again, now can be watched from the desktop client.
I migrated our users from another fine program "MindTouch" and since Cyn.in is such a more sophisticated user interface I was worried that my sometimes hesitant users would have a hard time. The first day I was live I received a call from one of our remote locations saying, and I do quote: " This is amazing, I click on a file and it's here in seconds. Really amazing!".
Less than two months into production my users are maintaining all their new documentation on the Cyn.in server, regularly watching the training videos and posting discussions in Cyn.in and the desktop client to find equipment and implements (We are a Bobcat, Toro & Kubota Dealership) at other locations.
We can easily post video and photos of equipment and copy the links to customers to see instead of moving equipment around.
I can't say enough good about this application that has been offered to the open source community.
People are currently mainly working with discussions, blog articles to publish knowledge, and links object to post public references on the net.
The problem is the product looks pretty dead, not updated for a while, and I'm getting very concerned, as people are using it more and more in my company, migration would be long and painful.
I'm not looking for features for now, just for a working product where discussion titles are actually displayed in lists, where date and time are displayed on items, basic things like this. I think Cynapse really need to consolidate foundation before moving on, I mean if the product is still under development.
Is this really 2011 soon ?