If you want to look at the differences in the content management system and the document management system in the real world, what is the best example?
Thanks for your attention. I’m looking forward to your reply.
There is a big difference between the content management and document management system. Name of both the services or tools seems to be same but there is a difference
CMS ( Content Management System)
The content management system is the tool which is used to maintain the content of a website or the application. Let me elaborate you in details
Have you ever create a website? A website is developed in Wordpress or in different things like Shopify, Magento etc. This kind of things are included in a content management system
Document Management System (DMS)
Document management system is used in the business/company or for individuals.
In DMS all the papers or documents are converted into the digital form by scanning them and saved all the documentation in the cloud server which will never be lost or theft.
All the business document are secured.
Content management systems vary from document management systems in one key area – the type of information they manage.
Document management system is designed specifically for data contained in structured documents and files like Word, PowerPoint, Excel spreadsheets, PDF, and other popular formats. Their purpose is primarily to digitize and archive files and track and manage new documents throughout their lifecycle, as they are written, revised, and updated. Many of them include advanced imaging and scanning capabilities (for digitization of hard copy files), that can’t be found in most content management systems.
Content management systems, on the other hand, are more about the logical organization and improved accessibility of various types of structured and unstructured electronic information. This includes not only the kinds of files that are managed by document management applications but a broader range of digital assets. For example, audio, video, Flash, and multimedia files, as well as raw data collected from various third-party Internet sources.
Related
I have hundreds of thousands of PDFs that are presently stored in the filesystem. I have a custom application that, as an afterthought to its actual purpose, provides access to these PDFs. I would like to take the "storage & retrieval" part out of the custom application and use an OpenSource document storage backend.
Access to the PDF Store should be via a REST API, so that users would not need a custom client for basic document browsing and viewing. Programs that store PDFs should also be able to work via the REST API. They would provide the actual binary or ASCII data plus structured meta data, which could later be used in retrieval.
A typical query for retrieval would be "give me all documents that were created between days X and Y with document types A or B".
My research, whether such a storage backend exists, has come up empty. Do any of you know a system that provides these features? OpenSource preferred, reasonably priced systems considered.
I am not looking for advice on how to "roll my own" using available technologies. Rather, I'm trying to find out whether that can be avoided. Many thanks in advance.
What you describe sounds like a document management or asset management system of which there are many; and many work with PDF files. I have some fleeting experience with commercial offerings such as Xinet (http://www.northplains.com/xinet - now acquired apparently) or Elvis (http://www.elvisdam.com). Both might fit your requirements but they're probably too big and likely too expensive.
Have you looked at Alfresco? This is an open source alternative I came into contact with years ago while being on the board of a selection committee. As far as I remember it definitely goes in the direction of what you are looking for and it is open source so might fit that angle as well: http://www.alfresco.com.
We are done migrating a website from old CMS to SDL Tridion. We have thousands of clients out of which fewer than five are migrated. Now let's say we need to automate migrating the rest of the thousands clients, obviously we can not use manual effort. Is there a way to develop automated solution against SDL using any APIs it may provide? If yes where can we find documentation for APIs? Any Books or online tutorials for the same?
all very technical answers. Whatever route you choose you need to weigh up the option of not doing a technical migration (and trying to get that right) versus employing a load of students to copy and paste.
Regardless of the CMS, the complexity of a migration can be measured based on how organized is your content in the system you want to migrate from.
I categorize the migration into 3 types related to the Origin and Destination:
1--> CMS to CMS
2--> Database to CMS
3--> WebSite to CMS
If the original source is a database or another CMS typically the complexity is reduced, as the content is already structured.
You have to extract that and map the existing content with the structure that will have in the new system
If the goal is migrate an existing website into a CMS the complexity increases as the content is more disorganized that
having that in the CMS.
Again, if the content in the site is properly structured is still possible to automate that, but most of the cases are old sites
maintained manually.
There are commercial tools that crawl the content from the sites and apply patterns to identify common elements, common content, common metadata, structure
and are able to massage the original content and apply logic based on rules that allows to structure the content, however even the best tool has a hard
work to do when the source is disorganized.
Also I have seen migrations that cut the final html in pieces and put that in the CMS. That is an easy approach but of course a wrong one, as
you are not taking any advantage of the CMS
And 3 Types related the source type we migrate from and the source type we want to obtain
1--> Content to Content
2--> (HTML + Content All together) into (HTML) + (Content) separated
3--> (HTML + Content + Code All together) into (HTML) + (Content) +
(Code) separated
Content to Content Migration is less complex
Second option is of course more complex, as you have to Separate Content and HTML that will become templates
Third option is even more complex, as if you are extracting the html of the page (using an http client for instance as most of the commercial tools do),
you are not capturing the logic of the page. For this case you need to work at the file level
Try to do a very depth analysis before you enter in a migration, as things can turn complex.
Only if you have a very good knowledge of the original system and solid patterns to apply you can think in an automation
Tridion has extensive APIs and these are thoroughly documented. Your starting point for SDL Tridion 2011 is https://www.sdltridionworld.com/downloads/documentation/SDLTridion2011SP1/index.aspx
Automated migrations are perfectly possible, however API support is not the limiting factor here. Understanding your data in your source and target scenarios is much more important.
I would consider contacting Kapow or Vamosa who both specialize in crawling sites and then importing them to a CMS. They both have connectors for SDL Tridion. This may save your clients both time and money.
Every migration is different, unless you are migrating "thousands of" sites (assuming a client is a site) from same source type to same destination (SDL Tridion in this case) with extremely close data models. Several SDL Tridion partners are already solving this problem and built/building assisted migration automation tools. Get in touch with us if you need more information.
I am using Scantron Cognition Enterprise at work to capture data from scanned forms. Building these forms is tedious at best, especially when it would be nice to have a library of pre-built objects to use. Unfortunately, documentation and on-line resources are scarce.
Does anyone have any pointers to find some resources for this tool?
Hey Jason, believe it or not, Scantron is STILL the standard, but this is not the Scantron you probably remember. Although OMR (bubble) forms are still used extensively in education, there are a lot more advanced technologies available to be added to them today.
Concerning Cognition, I looked through the available tags and these would fit:
"document-imaging" - Cognition is a document imaging product and can feed images and index values into most commercially available document storage applications
"OCR" - Optical Character Recognition, or reading machine print.
"ICR" - Intelligent Character Recognition - reading hand writing, usually in a constrained print format (one letter per box like a credt card application.
"datacollection" - the key purpose of Cognition is data collection.
However, there is not a tag for "OMR" - Optical Mark Recognition, or reading bubble choices, similar to the basic Scantron forms of the past. Also, I could not find one for "Key From Image", another purpose that Cognition is used for.
I am a Cognition user as well as someone who markets it and I know that there are a large number of users in North America. Many corporations that use Cognition use it for sensitive HR functions and so might not have their usage of it posted in a searchable format. Many other organizations use it for safety inspections, insurance data entry, and also for testing and surveys - basically anywhere you have a large number of paper forms and need all of the data quickly entered into a database. Many users are using Cognition for sensitive applications are so are not likely to share, but I can share a few I have, you could also contact your Scantron rep and they might have something they could share as well. I have some decent ICR fields built for name, e-mail, address, etc. The ICR fields are best when you build in your own dictionary or database look-ups. The OMR fields are the hard ones to build, but I have a few of these as well. The easiest way to share these is to send you the form that already has the field built into it. You can build your own lookups from txt, xls or db files.
I need to set up a CMS for our marketing dept. Basically they need a system that they can
sharing documents with multiple users
editing documents with multiple users
tracking changes
tracking/keeping multiple versions
storing and organizing files
The types of documents are : Illustrator, Photoshop, Pdf, MS word and Excel.
I am in the process of evaluating different CMS to use. Since we are a .Net shop so the first requirement is Windows based. I know we can use Windows SharePoint Services 3.0 or DotNetNuke.
Could anyone give me some suggestion? Thanks a lot!
I don't think you're looking for a CMS so much as a DMS (Document Management System). CMS are usually used for managing web-based content as opposed to documents, or if they do document management they usually do a poor job at it.
For basic management of Illustrator, Photoshop, Pdf, MS word and Excel documents I would look to something along the lines of SharePoint - it will suit your needs well for the PDF / Office documents, though I'm not sure how well it does with Illustration / Photoshop files - I'm sure it will store them but you might not have the full advantage of indexing provided by Sharepoint.
SiteCore is a tad bit on the expensive side, but for what it does it's well worth the investment. I've had a demo of the application and was very impressed with what SiteCore offers for end users. The application is developed in .net so any asp.net developers will be able to add, adjust and modify different items for you.
You've spoke about digital assest management, well here is Razuna, it's an open source digital assest management system that has several kinds of downloads to play with, one even being a pre-setup Virtual Image which can get you started right away. Take a look at it and see what you think.
Good luck on your search, and hope this helped some.
I'd consider Google Docs to begin with.
Otherwise, SharePoint can handle the office documents fairly well. If it's just for the marketing team, the 'free' Windows Sharepoint Services should suffice.
You may then want to look into Adobe Version Cue to handle the Adobe based art files.
An alternative thought would be to consider Version Control, so for example Subversion could work for storing changes, keeping track of changes, etc.
Percussion CMS is a GREAT marketing tool, someone recommended Document Management System for your applications you want to integrate and use with your CMS however; the key word is marketing tool. Percussion CMS is a great investment tool to help establish your online presence! With solutions like community marketing, personalization and web analytics these solutions are geared to generate a response from site users. Community marketing helps to engage socially with your visitors in facebook, twitter and community forums. Personalization helps with brand identity, features including product promotion and help your site's represent your company the way you want to be perceived. Lastly web analytics track users and report data back to marketers including information on bounce rates and geo-tracking. Reports showing whose visiting your site and their behaviors. Most importantly the Web CMS is fool proof. It is not code based or needs a webmaster to publish the content for your website. It's extremely user friendly.
We have a web application which contains a bunch of content that the system operator can change (e.g. news and events). Occasionally we publish new versions of the software. The software is being tagged and stored in subversion. However, I'm a bit torn on how to best version control the content that may be changed independently. What are some mechanisms that people use to make sure that content is stored and versioned in a way that the site can be recreated or at the very least version controlled?
When you identify two set of files which have their own life cycle (software files on one side, "news and events" on the other, you know that:
you can not versionned them together at the same time
you should not put the same label
You need to save the "news and event" files separatly (either in the VCS or in a DB like Ian Jacobs suggests, or in a CMS - Content Management system), and find a way to link the tow together (an id, a timestamp, a meta-label, ...)
Do not forget you are not only talking about two different set of files in term of life cycle, but also about different set of files in term of their very natures:
Consider the terminology introduced in this SO question "Is asset management a superset of source control" by S.Lott
software files: Infrastructure information, that is "representing the processing of the enterprise information asset". Your code is part of that asset and is managed by a VCS (Version Control System), as part of the Configuration management discipline.
"news and events": Enterprise Information, that is data (not processing); this is often split between Content Managers and Relational Databases.
So not everything should end up in Subversion.
Keep everything in the DB, and give every transaction to the DB a timestamp. that way you can keep standard DB backups and load the site content at whatever date you want if the worst happens.
I suppose part of the answer depends on what CMS you're using, and how your web app is designed, but in general, I'd regard data such as news items or events as "content". In other words, it's not part of your application - it's the data which your application processes.
Of course, there will be versioning issues between your CMS code and your application code. You could manage this by defining the interface between the two. Personally, I'd publish the data to the web app as XML, which gives you the possibility of using XML schema to define exactly what the CMS is required to produce, and what the web app should expect to process.
This ought to mean that most changes in the web app can be made without a corresponding alteration in the rendering of the data. When functionality changes require this, you can create a new version of the schema and continue to make progress. In this scenario, I'd check the schema in with the web app code, but YMMV.
It isn't easy, and it gets more complicated again if you need additional data fields in your CMS. Expect to plan for a fairly complex release process (also depending on how complex your Dev-Test-Acceptance-Production scenario is.)
If you aren't using a CMS, then you should consider it. (Of course, if the operation is very small, it may still fall into the category where doing it by hand is acceptable.) Simply putting raw data into a versioning system doesn't solve the problem - you need to be able to control the format in which your data is published to the web app. Almost certainly this format should be something intended for consumption by software, and therefore not usually suitable for hand-editing by the kind of people who write news items or events.