CUST-3 Document Management with Share
0 likes415 views
The document outlines an approach to application design focusing on repository and web tier customizations, including development tips and functionality definitions. It emphasizes the importance of information architecture and suggests taking time to learn the complexities of the Share interface. Additionally, it covers various customizations such as metadata templates, permissions management, and provides insights from a related blog post by Mike Hatfield.
CUST-3 Document Management with Share
- 2. Overview Approach to Application Design with Share Some tips picked up along the way Repository Tier Customizations Web Tier Customizations • Indicators • Metadata Templates • Actions Demo
- 3. Approach to Designing Solutions Start with the Information Architecture • Content Model • Folder Structure • Security/Permission Model Define functionality • Define Webscripts • Build out Services • Expose Javascript APIs • Build workflows Build the UI • CRUD Screens • Dashlets • Forms
- 4. Some Things That I Picked Up Along the Way • Do not lock yourself into the Collaboration Information Architecture if it is not appropriate • Share is not easy – Allocate time to learn it if you are using it as a UI • Remember that the Slingshot Webscripts are internal, do not write client code against them. • Take the time to understand the configuration • Learn how to Write YUI components. • A lot of significant improvements were added in 4.0.
- 5. Coding Example • We will cover some common customizations. • We have an example that we will use in this talk and in tomorrow’s talk • There are some missing pieces (YUI code).
- 6. Repository Extensions Document Library Custom Response • This allows the repository tier to return additional custom metadata about the repository Property Decorators • This alters the JSON format returned for nodes. Permissions List • This allows you to control the list of permissions that are sent back for each document.
- 7. Web Tier Extensions Status Indicators • Gives the developer control over the icons that get displayed based upon each status Metadata Templates • Gives the developer the ability to define custom templates for each content type Actions • This gives the developer the ability to control what actions are allowed for each document/folder. • The actions can be filtered based upon permissions Client dependencies • Provides an easy way to add JavaScript and CSS to the web tier.
- 8. DEMO
- 9. Additional Resources Mike Hatfield’s blog post that this was the inspiration for this talk. http://blogs.alfresco.com/wp/mikeh/2011/09/26/share- document-library-extensions-in-v4-0/