Does Alfresco support these features ?

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-20-2011 12:49 AM
1. Content Creation (Acquisition, Aggregation, Authoring)
• Acquisition
◦ Native support for filetypes
◦ Multiple file transfers (FTP, site import)
◦ Migration Tools (from another CMS)
◦ Conversion tools (e.g.,Word to XML "chunks")
◦ Rights management
◦ Workgroup management
◦ Facilities management
◦ Mandatory metadata tagging (force structure and semantics)
◦ RDF ontology support (e.g., Dublin Core)
• Aggregation
◦ Incoming syndication feeds
◦ Metadata management (read incoming metadata)
◦ Integrated Web Services (e.g., currency conversion)
◦ UDDI tools
• Authoring (Editing, Templating, Tagging Tools)
◦ Content Element Editors (Naive and Power Users)
■ WYSIWYG Through-The-Web Editor
■ Source Editor
■ Structured Fields Editor
■ XML Editor
■ Spell checker
■ Content objects use templates
■ Media asset repository (images, sounds, Flash, video, etc.)
◦ Template Editor
■ WYSIWYG Through-The-Web
■ Template Gallery
■ XML Editor
◦ Tag Editor (semantics and style)
■ Drop-down menus of all tags
■ Metadata Thesaurus
■ Taxonomies/Ontologies online
◦ Help online
■ Context-sensitive help
■ Documentation
2. Content Management Proper (Workflow, Editing, Approvals, Staging, Repository, etc.)
• Workflow
◦ Access Permission Levels (Privilege granularity)
■ Number of levels
■ Per User, Per Folder, Per Role, Per file, Per Content Element
■ Flexible assignments to workflow
■ Creator automatic owner of content
■ User subscription to workflow
■ LDAP Support
◦ Check In/Check Out
■ Open page on web (Edit this page)
■ Automatic file lock on open
■ Conflict Resolution (who has it?)
■ Instant Messaging (email, phones)
■ Merge Tools, Diff Tools
◦ View/Download
■ Download as PDF
◦ Workflow Messaging
■ Email notifications (links to work)
■ Status (stage in workflow)
■ Comments at each stage
■ Audit trail (workflow log)
◦ Arbitrary Roles (Writers, Editors, Graphic Artists, Rights Managers, Publishers, etc.)
• Versioning
◦ Scheduling, Expiration
◦ All elements, templates date/time stamped
◦ Archive with rollback (per file or site?)
• Personalization
◦ Identity Management
◦ Relationship Management (History)
◦ Actions tracking
◦ Session/Click/Behavior analysis
• Localization
◦ Multilingual server
■ Respond to browser language requests
■ Gist translation option
◦ Workflow
■ Automatic notifications
■ Quality checkers
◦ UI multilingual
• Reporting
◦ Chrono workflow and by worker
◦ WebTrends-style for whole site
◦ Specific monitors
◦ Performance (page delivery times)
• Storage
◦ Format (text, HTML, XML)
◦ Database only
◦ Files
◦ Files and database
• Backup
◦ Onsite and offsite
◦ Files and database
◦ To nonvolatile media
◦ Disaster recovery plan
• Security
◦ Firewall rules
◦ Encrypted sessions
• Staging Server for QA
◦ Testing methodology
◦ Replicates publishing environment
3. Content Delivery (Live Server, Publishing, Syndication)
• Publishing (Delivery)
◦ Separate Delivery from Creation/Staging/Testing
■ Use different server platform?
■ Replication
■ Synchronization of mirror sites
◦ Multi-channel Publishing to different clients
■ PDAs
■ Cell phones
■ Handicap accessibility
• Syndication
◦ RDF and RSS Syndicated News Feeds
◦ Web services
4. Lifecycle enhancements (Apply to all three stages above)
• Security
◦ Audit Trails
◦ Users
◦ System
◦ Network
• Business Rules
◦ Records Policy
◦ Privacy Policy
• Integration
◦ Single Source Of Truth (Single Sign On, Single Authentication)
◦ Enterprise portal
◦ Legacy database reuse
◦ Data warehousing
• Metadata management
◦ Digital rights management
◦ Business process management
• Associations
◦ Hierarchy, taxonomy
◦ Index
◦ Cross reference
• Analysis
◦ Analytic tools
◦ Pattern recognition
• Search and Locate
Pls let me know whether alfresco support these features
Labels:
- Labels:
-
Archive
2 REPLIES 2
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-20-2011 04:10 AM
Here's my best guess. Although I suggest you research the documentation before posting such a wide ranging and vague set of questions.
1. Content Creation (Acquisition, Aggregation, Authoring)
• Acquisition
What does that mean
◦ Native support for filetypes
Yes
◦ Multiple file transfers (FTP, site import)
Yes
◦ Migration Tools (from another CMS)
External tools are available or just use one of the filesystem protocols.
◦ Conversion tools (e.g.,Word to XML "chunks")
Probably, but what are XML "chunks".
◦ Rights management
Yes
◦ Workgroup management
Yes
◦ Facilities management
What's that?
◦ Mandatory metadata tagging (force structure and semantics)
Yes
◦ RDF ontology support (e.g., Dublin Core)
Yes, Dublin Core is provided as a sample.
• Aggregation
Yes
◦ Incoming syndication feeds
RSS feeds are supported is that what you mean?
◦ Metadata management (read incoming metadata)
Yes
◦ Integrated Web Services (e.g., currency conversion)
Not sure what you mean here.
◦ UDDI tools
Yes.
This lot may be N/A … In general you would use a third party tool.
• Authoring (Editing, Templating, Tagging Tools)
◦ Content Element Editors (Naive and Power Users)
■ WYSIWYG Through-The-Web Editor
Yes for some content types.
■ Source Editor
Yes.
■ Structured Fields Editor
Yes
■ XML Editor
■ Spell checker
■ Content objects use templates
■ Media asset repository (images, sounds, Flash, video, etc.)
◦ Template Editor
■ WYSIWYG Through-The-Web
■ Template Gallery
■ XML Editor
◦ Tag Editor (semantics and style)
■ Drop-down menus of all tags
■ Metadata Thesaurus
■ Taxonomies/Ontologies online
◦ Help online
■ Context-sensitive help
Some
■ Documentation
Yes
2. Content Management Proper (Workflow, Editing, Approvals, Staging, Repository, etc.)
• Workflow
◦ Access Permission Levels (Privilege granularity)
Yes
■ Number of levels
Yes
■ Per User, Per Folder, Per Role, Per file, Per Content Element
Yes, except Content Element
■ Flexible assignments to workflow
Yes
■ Creator automatic owner of content
Yes
■ User subscription to workflow
Yes
■ LDAP Support
Yes
◦ Check In/Check Out
■ Open page on web (Edit this page)
Yes
■ Automatic file lock on open
Yes
■ Conflict Resolution (who has it?)
Some support, in general alfresco tries to prevent the need in the first place.
■ Instant Messaging (email, phones)
Yes
■ Merge Tools, Diff Tools
Use third party tools.
◦ View/Download
■ Download as PDF
Yes
◦ Workflow Messaging
■ Email notifications (links to work)
Yes
■ Status (stage in workflow)
Yes
■ Comments at each stage
User workflow dependent.
■ Audit trail (workflow log)
Worlflow dependent.
◦ Arbitrary Roles (Writers, Editors, Graphic Artists, Rights Managers, Publishers, etc.)
Yes.
• Versioning
◦ Scheduling, Expiration
Yes.
◦ All elements, templates date/time stamped
Yes of you want it.
◦ Archive with rollback (per file or site?)
Yes
• Personalization
Yes
◦ Identity Management
Yes
◦ Relationship Management (History)
Yes
◦ Actions tracking
Can be done through Audit,
◦ Session/Click/Behavior analysis
No - except for through Audit.
• Localization
Yes
◦ Multilingual server
Yes
■ Respond to browser language requests
Yes
■ Gist translation option
Sorry, don't know what that is…
◦ Workflow
■ Automatic notifications
Yes
■ Quality checkers
What do you mean
◦ UI multilingual
Yes
• Reporting
Third party
◦ Chrono workflow and by worker
Yes
◦ WebTrends-style for whole site
No
◦ Specific monitors
No
◦ Performance (page delivery times)
Third party tools
• Storage
◦ Format (text, HTML, XML)
◦ Database only
Its possible, however
◦ Files
◦ Files and database
Yes
• Backup
Yes
◦ Onsite and offsite
That's up to you
◦ Files and database
See above
◦ To nonvolatile media
That's up to you.
◦ Disaster recovery plan
That's your responsibility
• Security
◦ Firewall rules
Yes
◦ Encrypted sessions
Yes
• Staging Server for QA
If you want
◦ Testing methodology
What do you mean
◦ Replicates publishing environment
Yes
3. Content Delivery (Live Server, Publishing, Syndication)
• Publishing (Delivery)
◦ Separate Delivery from Creation/Staging/Testing
■ Use different server platform?
Yes
■ Replication
Yes
■ Synchronization of mirror sites
Yes
◦ Multi-channel Publishing to different clients
■ PDAs
Yes
■ Cell phones
Yes
■ Handicap accessibility
Yes - some
• Syndication
◦ RDF and RSS Syndicated News Feeds
Yes
◦ Web services
Yes
4. Lifecycle enhancements (Apply to all three stages above)
What do you mean ?
• Security
◦ Audit Trails
◦ Users
◦ System
◦ Network
• Business Rules
◦ Records Policy
◦ Privacy Policy
• Integration
◦ Single Source Of Truth (Single Sign On, Single Authentication)
◦ Enterprise portal
◦ Legacy database reuse
◦ Data warehousing
• Metadata management
Yes
◦ Digital rights management
No. Although you could use a third party solution
◦ Business process management
Yes
• Associations
Yes
◦ Hierarchy, taxonomy
Yes
◦ Index
Yes
◦ Cross reference
Yes
• Analysis
What do you mean?
◦ Analytic tools
What do you mean?
◦ Pattern recognition
Yes
• Search and Locate
Yes
1. Content Creation (Acquisition, Aggregation, Authoring)
• Acquisition
What does that mean
◦ Native support for filetypes
Yes
◦ Multiple file transfers (FTP, site import)
Yes
◦ Migration Tools (from another CMS)
External tools are available or just use one of the filesystem protocols.
◦ Conversion tools (e.g.,Word to XML "chunks")
Probably, but what are XML "chunks".
◦ Rights management
Yes
◦ Workgroup management
Yes
◦ Facilities management
What's that?
◦ Mandatory metadata tagging (force structure and semantics)
Yes
◦ RDF ontology support (e.g., Dublin Core)
Yes, Dublin Core is provided as a sample.
• Aggregation
Yes
◦ Incoming syndication feeds
RSS feeds are supported is that what you mean?
◦ Metadata management (read incoming metadata)
Yes
◦ Integrated Web Services (e.g., currency conversion)
Not sure what you mean here.
◦ UDDI tools
Yes.
This lot may be N/A … In general you would use a third party tool.
• Authoring (Editing, Templating, Tagging Tools)
◦ Content Element Editors (Naive and Power Users)
■ WYSIWYG Through-The-Web Editor
Yes for some content types.
■ Source Editor
Yes.
■ Structured Fields Editor
Yes
■ XML Editor
■ Spell checker
■ Content objects use templates
■ Media asset repository (images, sounds, Flash, video, etc.)
◦ Template Editor
■ WYSIWYG Through-The-Web
■ Template Gallery
■ XML Editor
◦ Tag Editor (semantics and style)
■ Drop-down menus of all tags
■ Metadata Thesaurus
■ Taxonomies/Ontologies online
◦ Help online
■ Context-sensitive help
Some
■ Documentation
Yes
2. Content Management Proper (Workflow, Editing, Approvals, Staging, Repository, etc.)
• Workflow
◦ Access Permission Levels (Privilege granularity)
Yes
■ Number of levels
Yes
■ Per User, Per Folder, Per Role, Per file, Per Content Element
Yes, except Content Element
■ Flexible assignments to workflow
Yes
■ Creator automatic owner of content
Yes
■ User subscription to workflow
Yes
■ LDAP Support
Yes
◦ Check In/Check Out
■ Open page on web (Edit this page)
Yes
■ Automatic file lock on open
Yes
■ Conflict Resolution (who has it?)
Some support, in general alfresco tries to prevent the need in the first place.
■ Instant Messaging (email, phones)
Yes
■ Merge Tools, Diff Tools
Use third party tools.
◦ View/Download
■ Download as PDF
Yes
◦ Workflow Messaging
■ Email notifications (links to work)
Yes
■ Status (stage in workflow)
Yes
■ Comments at each stage
User workflow dependent.
■ Audit trail (workflow log)
Worlflow dependent.
◦ Arbitrary Roles (Writers, Editors, Graphic Artists, Rights Managers, Publishers, etc.)
Yes.
• Versioning
◦ Scheduling, Expiration
Yes.
◦ All elements, templates date/time stamped
Yes of you want it.
◦ Archive with rollback (per file or site?)
Yes
• Personalization
Yes
◦ Identity Management
Yes
◦ Relationship Management (History)
Yes
◦ Actions tracking
Can be done through Audit,
◦ Session/Click/Behavior analysis
No - except for through Audit.
• Localization
Yes
◦ Multilingual server
Yes
■ Respond to browser language requests
Yes
■ Gist translation option
Sorry, don't know what that is…
◦ Workflow
■ Automatic notifications
Yes
■ Quality checkers
What do you mean
◦ UI multilingual
Yes
• Reporting
Third party
◦ Chrono workflow and by worker
Yes
◦ WebTrends-style for whole site
No
◦ Specific monitors
No
◦ Performance (page delivery times)
Third party tools
• Storage
◦ Format (text, HTML, XML)
◦ Database only
Its possible, however
◦ Files
◦ Files and database
Yes
• Backup
Yes
◦ Onsite and offsite
That's up to you
◦ Files and database
See above
◦ To nonvolatile media
That's up to you.
◦ Disaster recovery plan
That's your responsibility
• Security
◦ Firewall rules
Yes
◦ Encrypted sessions
Yes
• Staging Server for QA
If you want
◦ Testing methodology
What do you mean
◦ Replicates publishing environment
Yes
3. Content Delivery (Live Server, Publishing, Syndication)
• Publishing (Delivery)
◦ Separate Delivery from Creation/Staging/Testing
■ Use different server platform?
Yes
■ Replication
Yes
■ Synchronization of mirror sites
Yes
◦ Multi-channel Publishing to different clients
■ PDAs
Yes
■ Cell phones
Yes
■ Handicap accessibility
Yes - some
• Syndication
◦ RDF and RSS Syndicated News Feeds
Yes
◦ Web services
Yes
4. Lifecycle enhancements (Apply to all three stages above)
What do you mean ?
• Security
◦ Audit Trails
◦ Users
◦ System
◦ Network
• Business Rules
◦ Records Policy
◦ Privacy Policy
• Integration
◦ Single Source Of Truth (Single Sign On, Single Authentication)
◦ Enterprise portal
◦ Legacy database reuse
◦ Data warehousing
• Metadata management
Yes
◦ Digital rights management
No. Although you could use a third party solution
◦ Business process management
Yes
• Associations
Yes
◦ Hierarchy, taxonomy
Yes
◦ Index
Yes
◦ Cross reference
Yes
• Analysis
What do you mean?
◦ Analytic tools
What do you mean?
◦ Pattern recognition
Yes
• Search and Locate
Yes
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-20-2011 04:30 AM
It's a common "CMS Feature" list that does the rounds. Potential source: http://www.cmsreview.com/Features/Lists.html
To kvramalingeswararao: I suggest you look at the real requirements your potential customer has rather than taking such a generic list for product comparison.
Mike
To kvramalingeswararao: I suggest you look at the real requirements your potential customer has rather than taking such a generic list for product comparison.
Mike
