Aspect cm:temporary is sometimes very useful. If you want to delete a node immediately without moving the node to paper bin (archive store) adding cm:temporary aspect before deletion solves your prob. Nodes with cm:temporary attached will deleted without detour via paper bin:

Java:

nodeService.addAspect(nodeRef, ContentModel.ASPECT_TEMPORARY, null);
nodeService.deleteNode(nodeRef);

JS:

mynode.addAspect(“cm:temporary”);
mynode.remove();

Have Fun!

Sometimes these tagScopeCache are out-of-sync (at least in Alfresco 3.1), so I wrote a simple Javascript snippet to refresh this caches:

function refreshTagScope(folder){
var refresh = actions.create("refresh-tagscope");
refresh.execute(folder);
for each(item in folder.children)
{
if (item.isContainer)
{
refreshTagScope(item);
}
}
}
refreshTagScope(space);

Steps to use this script:

1. Upload js to data dictionary / Scripts
2. navigate in JSF client to site or site container where you want to refresh your tagScopeCache
3. open details page of folder
4. Run Action -> Execute Script & choose the uploaded script.

Topic of this post is a little bit different. My idea raised a year ago, but I realized that I won’t do it myself…idea?

here it is:

There are plenty of Alfresco partners worldwide & also a lot of interesting projects are going on. My motto was (& still is) learning by doing, hands on. So why not doing something I’m calling “Alfrescian World Tour”:
One year participating in Alfresco projects around the world, at least one in each continent! Joining for 1 or 2 month a project, learn a lot of new topics & then go to the next project. Thanks to twitter, blogs etc. it will be no problem to find interesting projects and perhaps Nancy Garrity (Alfresco Community Manager) is able to support this Tour somehow. After finishing the tour I wanted to write a book about it…

I think this will be a nice travel for a graduate taht wants to gain a lot of knowledge in Alfresco and ECM. I haven’t discussed this with my boss, but I think i can offer a 1-2 month project at westernacher in Germany.

So, Alfrescians: Is there anybody out there?

Now, I’m wondering if it is a nice idea to add sth. like a internal twitter system to Share. Alfresco’s Activity Feed is a nice approach to track each activity, but in a system with more than hundred members of a site this feed gets very chattering. So, my basic idea:

• reuse twitter syntax (@, DM, RT & #)
• # –> automatically tag the message
• twitter user-dashlet (like BeTwittered Google Gadget)
• site-dashlet: last messages of site members
• action link in DocLib, wiki etc. “recommed via twitter”:
  - opens dialog to write twitter message
  - autocompletion for user names typing @ or DM
  - automatically add shortened link to content
• decide if each member follows all other site members or reuse twitter-like follow mechanism
• tbc

So…what do you think about this?

1. Upload a a new document to Share doclib, e.g. called test.doc
2. Upload another test.doc document with other content to the same space/folder via Share
3. What happened? The 2nd upload overwrites the first one, the content property has been replaced, the first test.doc content has gone…

Upps! Please don’t try this with your boss’s 200 page concept

I followed this in Enterprise 3.0.1 & Ent. 3.1…

I’ll raise an issue when I recover my  JIRA credentials.

What about Role based configuration? I think it is quite often that you’d like to configurate, that for example a consumer doesn’t see some adminitrative components or Dashlets you’ve added to Share to support your use case.

I know that you can achieve this by custom coding (Or am I missing sth.?), but from my point of view this should be an configuration task.

I’m sure, that the new REST based Form Service will help a lot of developers!

Here are the wireframes of the user stories at slideshare.

But I’m not sure if this is a real must for Share…I’m not sure if the user NEED this client. Of course Alfresco will gain a lot of marketing momentum offering an “iPhone-Enterprise-Collaboration” app. Does Sharepoint have sth. like that

BUT, from my point of view there are other 1st prio features enterprise customers really need:

• supporting custom Types, Aspects and Metadata  (docLib & search)
• group based site membership (& more permission stuff like, SiteCreatorGroup etc.)
• combination of Share & MS Sharepoint protocol usage within MS Office
• Support of Rules inside of Share

Most of these features are part of the Alfresco roadmap. Specially the support of custom types & aspects within Share is a real MUST.

I’m doing ECM-Projects since a while and I cannot remember a project where we used only basis types and metadata.

To sum up:
It’s cool that Alfresco is always developing new stuff, that’s why I love it. But from my point Share is lacking some features which should be done before going onwards with other new apps.

Beside GXT I wanted also to dive into the “CMIS world” and the best way to do this is always “hands on”!

Thus I’m just getting a new job (more Alfresco   I need to refresh my knowledge…). So I started 2 nights ago with my new project: Alfrescian CMIS browser!
It’s currently a little bit scrubby, but here is a first screenshot:

Some technical details:

• I’m using the CMIS AtomPub-Binding
• Folder tree & document grid using async GWT-RPC Services which are using Abdera libs to call the repo

opsoro started out as a Prototype and is still in an early state.  Nevertheless I encourage anyone who is familiar with alfresco to test opsoro client. Even if it is not production ready yet, it demonstrates the possibilities which lie in rich web applications and the Alfresco Web Script API

But, opsoro is more than a year ago. It is time for a new project! So stay tuned