Photo:1
Photo:2
Photo:3
Photo:4
Photo:1 Photo:2 Photo:3 Photo:4 |
| History | |
| 2>
This section does not cite any references or sources. Please help improve this section by adding citations to reliable sources. Unsourced material may be challenged and removed. (November 2009)
Beginning in the 1980s, a number of vendors began developing software systems to manage paper-based documents. These systems dealt with paper documents, which included not only printed and published documents, but also photographs, prints, etc.
Later developers began to write a second type of system which could manage electronic documents, i.e., all those documents, or files, created on computers, and often stored on users' local file-systems. The earliest electronic document management (EDM) systems managed either proprietary file types, or a limited number of file formats.[1] Many of these systems later[when?] became known as document imaging systems, because they focused on the capture, storage, indexing and retrieval of image file formats.EDM systems evolved to a point where systems could manage any type of file format that could be stored on the network. The applications grew to encompass electronic documents, collaboration tools, security, workflow, and auditing capabilities.
These systems enabled an organization to capture faxes and forms, to save copies of the documents as images, and to store the image files in the repository for security and quick retrieval (retrieval made possible because the system handled the extraction of the text from the document in the process of capture, and the text-indexer function provided text-retrieval capabilities).
EDM systems evolved to a point where systems could manage any type of file format that could be stored on the network. The applications grew to encompass electronic documents, collaboration tools, security, workflow, and auditing capabilities.
While many EDM systems store documents in their native file format (Microsoft Word or Excel, PDF), some web-based document management systems are beginning to store content in the form of html. These policy management systems[2] require content to be imported into the system. However, once content is imported, the software acts like a search engine so users can find what they are looking for faster. The html format allows for better application of search capabilities such as full-text searching and stemming.[3]
[edit] Tags:Reliable Sources,Challenged,Electronic Documents,Images,Document Imaging,Workflow,Cite,References Or Sources,File-systems,File Formats,Image File Formats,Collaboration Tools,Auditing,Repository,Text-retrieval,Html,Help, | |
| Components | |
| 2>
This section does not cite any references or sources. Please help improve this section by adding citations to reliable sources. Unsourced material may be challenged and removed. (November 2009)
Document management systems commonly provide storage, versioning, metadata, security, as well as indexing and retrieval capabilities. Here is a description of these components:
Topic
Description
Metadata
Metadata is typically stored for each document. Metadata may, for example, include the date the document was stored and the identity of the user storing it. The DMS may also extract metadata from the document automatically or prompt the user to add metadata. Some systems also use optical character recognition on scanned images, or perform text extraction on electronic documents. The resulting extracted text can be used to assist users in locating documents by identifying probable keywords or providing for full text search capability, or can be used on its own. Extracted text can also be stored as a component of metadata, stored with the image, or separately as a source for searching document collections.
Integration
Many document management systems attempt to integrate document management directly into other applications, so that users may retrieve existing documents directly from the document management system repository, make changes, and save the changed document back to the repository as a new version, all without leaving the application. Such integration is commonly available for office suites and e-mail or collaboration/groupware software. Integration often uses open standards such as ODMA, LDAP, WebDAV and SOAP to allow integration with other software and compliance with internal controls.[citation needed]
Capture
Capture primarily involves accepting and processing images of paper documents from scanners or multifunction printers. Optical character recognition (OCR) software is often used, whether integrated into the hardware or as stand-alone software, in order to convert digital images into machine readable text. Optical mark recognition (OMR) software is sometimes used to extract values of check-boxes or bubbles. Capture may also involve accepting electronic documents and other computer-based files.
Indexing
Indexing tracks electronic documents. Indexing may be as simple as keeping track of unique document identifiers; but often it takes a more complex form, providing classification through the documents' metadata or even through word indexes extracted from the documents' contents. Indexing exists mainly to support retrieval. One area of critical importance for rapid retrieval is the creation of an index topology.
Storage
Store electronic documents. Storage of the documents often includes management of those same documents; where they are stored, for how long, migration of the documents from one storage media to another (hierarchical storage management) and eventual document destruction.
Retrieval
Retrieve the electronic documents from the storage. Although the notion of retrieving a particular document is simple, retrieval in the electronic context can be quite complex and powerful. Simple retrieval of individual documents can be supported by allowing the user to specify the unique document identifier, and having the system use the basic index (or a non-indexed query on its data store) to retrieve the document. More flexible retrieval allows the user to specify partial search terms involving the document identifier and/or parts of the expected metadata. This would typically return a list of documents which match the user's search terms. Some systems provide the capability to specify a Boolean expression containing multiple keywords or example phrases expected to exist within the documents' contents. The retrieval for this kind of query may be supported by previously built indexes, or may perform more time-consuming searches through the documents' contents to return a list of the potentially relevant documents. See also Document retrieval.
Distribution
A published document for distribution has to be in a format that can not be easily altered. As a common practice in law regulated industries, an original master copy of the document is usually never used for distribution other than archiving. If a document is to be distributed electronically in a regulatory environment, then the equipment tasking the job has to be quality endorsed AND validated. Similarly quality endorsed electronic distribution carriers have to be used. This approach applies to both of the systems by which the document is to be inter-exchanged, if the integrity of the document is highly in demand.
Security
Document security is vital in many document management applications. Compliance requirements for certain documents can be quite complex depending on the type of documents. For instance, in the United States, the Health Insurance Portability and Accountability Act (HIPAA) requirements dictate that medical documents have certain security requirements. Some document management systems have a rights management module that allows an administrator to give access to documents based on type to only certain people or groups of people. Document marking at the time of printing or PDF-creation is an essential element to preclude alteration or unintended use.
Workflow
Workflow is a complex process and some document management systems have a built-in workflow module. There are different types of workflow. Usage depends on the environment the electronic document management system (EDMS) is applied to. Manual workflow requires a user to view the document and decide whom to send it to. Rules-based workflow allows an administrator to create a rule that dictates the flow of the document through an organization: for instance, an invoice passes through an approval process and then is routed to the accounts-payable department. Dynamic rules allow for branches to be created in a workflow process. A simple example would be to enter an invoice amount and if the amount is lower than a certain set amount, it follows different routes through the organization. Advanced workflow mechanisms can manipulate content or signal external processes while these rules are in effect.
Collaboration
Collaboration should be inherent in an EDMS. In its basic form, a collaborative EDMS should allow documents to be retrieved and worked on by an authorized user. Access should be blocked to other users while work is being performed on the document. Other advanced forms of collaboration allow multiple users to view and modify (or markup) a document at the same time in a collaboration session. The resulting document should be viewable in its final shape, while also storing the markups done by each individual user during the collaboration session.
Versioning
Versioning is a process by which documents are checked in or out of the document management system, allowing users to retrieve previous versions and to continue work from a selected point. Versioning is useful for documents that change over time and require updating, but it may be necessary to go back to or reference a previous copy.
Searching
Searching finds documents and folders using template attributes or full text search. Documents can be searched using various attributes and document content.
Publishing
Publishing a document involves the procedures of proofreading, peer or public reviewing, authorizing, printing and approving etc. Those steps ensure prudence and logical thinking. Any careless handling may result in the inaccuracy of the document and therefore mislead or upset its users and readers. In law regulated industries, some of the procedures have to be completed as evidenced by their corresponding signatures and the date(s) on which the document was signed. Refer to the ISO divisions of ICS 01.140.40 and 35.240.30 for further information.[4][5]
The published document should be in a format that is not easily altered without a specific knowledge or tools, and yet it is read-only or portable.[6]
Reproduction
Document/image reproduction is key when thinking about implementing a system. It's great to be able to put things in, but how are you going to get them out? An example of this is building plans. How will plans be scanned and scale be retained when printed?
[edit] Tags:Metadata,Optical Character Recognition,Office Suites,E-mail,Odma,Ldap,Webdav,Soap,Scanners,Multifunction Printers,Optical Mark Recognition,Topology,Hierarchical Storage Management,Boolean Expression,Document Retrieval,United States,Health Insurance Portability And Accountability Act,Versioning,Publishing,Proofreading,Peer,Prudence,Iso, | |
| Standardization | |
| 2>
Many industry associations publish their own lists of particular document control standards that are used in their particular field. Following is a list of some of the relevant ISO documents. Divisions ICS 01.140.10 and 01.140.20.[7][8] The ISO has also published a series of standards regarding the technical documentation, covered by the division of 01.110.[9]
ISO 2709 Information and documentation — Format for information exchange
ISO 15836 Information and documentation — The Dublin Core metadata element set
ISO 15489 Information and documentation — Records management
ISO 21127 Information and documentation — A reference ontology for the interchange of cultural heritage information
ISO 23950 Information and documentation — Information retrieval (Z39.50) — Application service definition and protocol specification
ISO 10244 Document management — Business process baselining and analysis
ISO 32000 Document management — Portable document format
[edit] Tags:Records Management,Technical Documentation,Ontology,Iso 32000,Documentation, | |
| Document control | |
| 2>
Compliance adds requirements that transform document management into a document control issue. Document control is a regulatory requirement within accounting (e.g., 8th EU Directive, Sarbanes-Oxley), food safety (e.g., Food Safety Modernization Act), ISO (mentioned above), medical device manufacturing (FDA), manufacture of blood, human cells, and tissue products (FDA), Healthcare (JCAHO), and Information technology (ITIL).[10][11] Your documents — procedures, work instructions, policy statements, etc. — provide evidence of documents under control. Failing to comply could cause fines, the loss of business, or damage to your business reputation.
The basic requirement for document control require that you establish and document a procedure for:
Reviewing and approving documents prior to release
Reviews and approvals
Ensuring changes and revisions are clearly identified
Ensuring that relevant versions of applicable documents are available at their “points of use”
Ensuring that documents remain legible and identifiable
Ensuring that external documents like customer supplied documents or supplier manuals are identified and controlled
Preventing “unintended” use of obsolete documents
[edit] Tags:Jcaho,Itil, | |
| See also | |
| 2>
Construction collaboration technology
Content management system
Data proliferation
Document automation
Documentation
Information repository
Information science
Intelligent document
Library science
Revision control
Taxonomy
Enterprise Content Management
[edit] Tags:Enterprise Content Management,Construction Collaboration Technology,Content Management System,Data Proliferation,Document Automation,Information Repository,Information Science, | |
| References | |
| 2>
^ Papergear: Electronic Document Management Systems
^ Policy Management System
^ Stemming: Making searching easier
^ International Organization for Standardization. "01.140.40: Publishing". http://www.iso.org/iso/products/standards/catalogue_ics_browse.htm?ICS1=01&ICS2=140&ICS3=40&. Retrieved 14 July 2008.
^ International Organization for Standardization. "35.240.30: IT applications in information, documentation and publishing". http://www.iso.org/iso/catalogue_ics_browse?ICS1=35&ICS2=240&ICS3=30&. Retrieved 14 July 2008.
^ OnSphere Corporation. "SOP Document Management in a Validated Environments". http://www.avidoffice.com/docushare/dsweb/Get/Document-9101/Standard%20Operation%20Procedure%20(SOP)%20Document%20Management%20in%20Validated%20Environments.pdf. Retrieved 25 April 2011.
^ International Organization for Standardization. "01.140.10: Writing and transliteration". http://www.iso.org/iso/products/standards/catalogue_ics_browse.htm?ICS1=01&ICS2=140&ICS3=10&. Retrieved 14 July 2008.
^ International Organization for Standardization. "01.140.20: Information sciences". http://www.iso.org/iso/products/standards/catalogue_ics_browse.htm?ICS1=01&ICS2=140&ICS3=20&. Retrieved 14 July 2008.
^ International Organization for Standardization. "01.110: Technical product documentation". http://www.iso.org/iso/products/standards/catalogue_ics_browse.htm?ICS1=01&ICS2=110&. Retrieved 15 July 2008.
^ Anderson, Chris. Is Document Control Really That Important?, Bizmanualz, December 17th, 2010.
^ "Code of Federal Regulations Title 21, Part 1271". Food and Drug Administration. http://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfcfr/CFRSearch.cfm?CFRPart=1271&showFR=1. Retrieved 31 January 2012.
[edit] Tags: | |
| External links | |
| 2>
Wikimedia Commons has media related to: Document management systems
Software/Document Management at the Open Directory Project
Miles L. Mathieu, Ernest A. Capozzoli (2002) (PDF). The Paperless Office: Accepting Digitized data. Troy State University. http://www.cabinetng.com/media/Paperless%20Office_Troy%20State.pdf.
Retrieved from "http://en.wikipedia.org/w/index.php?title=Document_management_system&oldid=475246351"
Categories: Information technology managementDocument management systemsHidden categories: Articles needing additional references from October 2008All articles needing additional referencesArticles needing additional references from November 2009Vague or ambiguous time from February 2011All articles with unsourced statementsArticles with unsourced statements from February 2007Use dmy dates from February 2011
Personal tools
Log in / create account
Namespaces
Article
Talk
Variants
Views
Read
Edit
View history
Actions
Search
Navigation
Main page
Contents
Featured content
Current events
Random article
Donate to Wikipedia
Interaction
Help
About Wikipedia
Community portal
Recent changes
Contact Wikipedia
Toolbox
What links here
Related changes
Upload file
Special pages
Permanent link
Cite this page
Print/export
Create a bookDownload as PDFPrintable version
Languages
Afrikaans
Česky
Deutsch
Ελληνικά
Español
فارسی
Français
한국어
Italiano
Lietuvių
Nederlands
日本語
Norsk (bokmål)
Polski
Português
Română
Русский
Slovenčina
Slovenščina
Svenska
ไทย
Türkçe
This page was last modified on 5 February 2012 at 17:01.
Text is available under the Creative Commons Attribution-ShareAlike License;
additional terms may apply.
See Terms of use for details.
Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization.Contact us
Privacy policy
About Wikipedia
Disclaimers
Mobile view
if ( window.isMSIE55 ) fixalpha();
if ( window.mediaWiki ) {
mw.loader.load(["mediawiki.user", "mediawiki.util", "mediawiki.page.ready", "mediawiki.legacy.wikibits", "mediawiki.legacy.ajax", "mediawiki.legacy.mwsuggest", "ext.gadget.wmfFR2011Style", "ext.vector.collapsibleNav", "ext.vector.collapsibleTabs", "ext.vector.editWarning", "ext.vector.simpleSearch", "ext.UserBuckets", "ext.articleFeedback.startup", "ext.articleFeedbackv5.startup", "ext.markAsHelpful"]);
}
if ( window.mediaWiki ) {
mw.user.options.set({"ccmeonemails":0,"cols":80,"date":"default","diffonly":0,"disablemail":0,"disablesuggest":0,"editfont":"default","editondblclick":0,"editsection":1,"editsectiononrightclick":0,"enotifminoredits":0,"enotifrevealaddr":0,"enotifusertalkpages":1,"enotifwatchlistpages":0,"extendwatchlist":0,"externaldiff":0,"externaleditor":0,"fancysig":0,"forceeditsummary":0,"gender":"unknown","hideminor":0,"hidepatrolled":0,"highlightbroken":1,"imagesize":2,"justify":0,"math":1,"minordefault":0,"newpageshidepatrolled":0,"nocache":0,"noconvertlink":0,"norollbackdiff":0,"numberheadings":0,"previewonfirst":0,"previewontop":1,"quickbar":5,"rcdays":7,"rclimit":50,"rememberpassword":0,"rows":25,"searchlimit":20,"showhiddencats":false,"showjumplinks":1,"shownumberswatching":1,"showtoc":1,"showtoolbar":1,"skin":"vector","stubthreshold":0,"thumbsize":4,"underline":2,"uselivepreview":0,"usenewrc":0,"watchcreations":1,"watchdefault":0,"watchdeletion":0,"watchlistdays":3,"watchlisthideanons":0,
"watchlisthidebots":0,"watchlisthideliu":0,"watchlisthideminor":0,"watchlisthideown":0,"watchlisthidepatrolled":0,"watchmoves":0,"wllimit":250,"flaggedrevssimpleui":1,"flaggedrevsstable":0,"flaggedrevseditdiffs":true,"flaggedrevsviewdiffs":false,"vector-simplesearch":1,"useeditwarning":1,"vector-collapsiblenav":1,"usebetatoolbar":1,"usebetatoolbar-cgd":1,"wikilove-enabled":1,"variant":"en","language":"en","searchNs0":true,"searchNs1":false,"searchNs2":false,"searchNs3":false,"searchNs4":false,"searchNs5":false,"searchNs6":false,"searchNs7":false,"searchNs8":false,"searchNs9":false,"searchNs10":false,"searchNs11":false,"searchNs12":false,"searchNs13":false,"searchNs14":false,"searchNs15":false,"searchNs100":false,"searchNs101":false,"searchNs108":false,"searchNs109":false,"gadget-wmfFR2011Style":1});;mw.user.tokens.set({"editToken":"+\\","watchToken":false});;mw.loader.state({"user.options":"ready","user.tokens":"ready"});
/* cache key: enwiki:resourceloader:filter:minify-js:4:b41a86ec4e0fe8329bc3ce917e792339 */
}
Tags: | |
zote monety click here click here click here click here |