Editing Document management system (section)

==Components==
Document management systems commonly provide storage, versioning, metadata, security, as well as indexing and retrieval capabilities. Here is a description of these components:

{| class="wikitable" document management system (section):
|-
! Topic !! Description
|-
| '''[[Metadata]]''' || [[Metadata]] is typically stored for each document. [[Metadata]] may, for example, include the date the document will be 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 document, or separately from the document as a source for searching document collections.<ref name="ParsonsEffective04">{{cite book |url=https://books.google.com/books?id=R_oRDAAAQBAJ&pg=PA234 |title=Effective Knowledge Management for Law Firms |last=Parsons |first=M. |publisher=Oxford University Press |page=234 |year=2004 |isbn=9780195169683 |access-date=19 May 2018}}</ref>
|-
| '''Integration''' || Many document management systems attempt to provide document management functionality directly to 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 a variety of software tools such as [[Workflow management system|workflow management]] and [[content management system]]s, typically through an [[application programming interface]] (API) using open standards such as [[ODMA]], [[Lightweight Directory Access Protocol|LDAP]], [[WebDAV]], and [[SOAP]] or [[Representational state transfer|RESTful]] web services.<ref name="ShivakumarEnter16">{{cite book |url=https://books.google.com/books?id=wFK9DQAAQBAJ&pg=PA93 |title=Enterprise Content and Search Management for Building Digital Platforms |last=Shivakumar |first=S.K. |publisher=John Wiley & Sons |page=93 |year=2016 |isbn=9781119206828 |access-date=19 May 2018}}</ref><ref name="FletcherWorkflow03">{{cite book |url=https://books.google.com/books?id=Z0VuXKlaLNcC&pg=PA16 |title=Workflow Management with SAP WebFlow: A Practical Manual |last1=Fletcher |first1=A.N. |last2=Brahm |first2=M. |last3=Pargmann |first3=H. |publisher=Springer Science & Business Media |pages=15–16 |year=2003 |isbn=9783540404033 |access-date=19 May 2018}}</ref>
|-
| '''Capture''' || Capture primarily involves accepting and processing images of paper documents from [[Image scanner|scanner]]s or [[multifunction printer]]s. [[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.<ref name="WebberITGov16">{{cite book |url=https://books.google.com/books?id=4OzyDAAAQBAJ&pg=SA41-PA4 |title=It Governance: Policies and Procedures |last1=Webber |first1=M. |last2=Webber |first2=L. |publisher=Wolters Kluwer |pages=41–4 |year=2016 |isbn=9781454871323 |access-date=19 May 2018}}</ref>
|-
| '''Data validation''' || Data validation rules can check for document failures, missing signatures, misspelled names, and other issues, recommending real-time correction options before importing data into the DMS. Additional processing in the form of harmonization and data format changes may also be applied as part of data validation.<ref name="TrinchieriEval03">{{cite book |title=Evaluation of Integrated Document Management System (IDMS) Options for the Arizona Department of Transportation (ADOT) |last=Trinchieri |first=D. |publisher=Arizona Department of Transportation |page=158 |year=2003 |quote="The data validation rules should be embedded in the form itself, rather than accomplished in a post-processing environment. This provides the use an interactive real-time experience. Often data validation requires a database look-up. The rules should allow this database query, providing the user real-time choices based on query results."}}</ref><ref name="MorleyUnder14">{{cite book |url=https://books.google.com/books?id=bDAeCgAAQBAJ&pg=PA558 |title=Understanding Computers: Today and Tomorrow, Comprehensive |last1=Morley |first1=D. |last2=Parker |first2=C.S. |publisher=Cengage Learning |pages=558–559 |year=2014 |isbn=9781285767277 |access-date=19 May 2018}}</ref>
|-
| '''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 information query and retrieval. One area of critical importance for rapid retrieval is the creation of an index [[topology]] or scheme.<ref name="MeurantInto12-1">{{cite book |url=https://books.google.com/books?id=lzGGHLDERYIC&pg=PA120 |title=Introduction to Electronic Document Management Systems |last=Meurant |first=G. |publisher=Academic Press |page=120 |year=2012 |isbn=9780323140621 |access-date=19 May 2018}}</ref>
|-
| '''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.<ref name="MeurantInto12-1" /> 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,<ref name="MeurantInto12-1" /> 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 document ready for distribution has to be in a format that cannot be easily altered. An original master copy of the document is usually never used for distribution; rather, an electronic link to the document itself is more common. If a document is to be distributed electronically in a regulatory environment, then additional criteria must be met, including assurances of traceability and versioning, even across other systems.<ref name="SommervilleImp06">{{cite book |url=https://books.google.com/books?id=QkUqBgAAQBAJ&pg=PA130 |title=Implementing IT in Construction |last1=Sommerville |first1=J. |last2=Craig |first2=N. |publisher=Routledge |page=130 |year=2006 |isbn=9781134198986 |access-date=19 May 2018}}</ref> This approach applies to both of the systems by which the document is to be inter-exchanged, if the integrity of the document is imperative.
|-
| '''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 of America|United States]], standards such as [[ISO 9001]] and [[ISO 13485]], as well as U.S. [[Food and Drug Administration]] regulations, dictate how the document control process should be addressed.<ref name="SkipperHowTo15">{{cite book |url=https://books.google.com/books?id=HLIDCwAAQBAJ&pg=PT10 |title=How to Establish a Document Control System for Compliance with ISO 9001:2015, ISO 13485:2016, and FDA Requirements |last=Skipper |first=S.L. |publisher=ASQ Quality Press |pages=156 |year=2015 |isbn=9780873899178 |access-date=19 May 2018}}</ref> Document management systems may 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 either a built-in workflow module<ref name="AusterberryDigital12-1">{{cite book |url=https://books.google.com/books?id=c5ncAwAAQBAJ&pg=PT35 |title=Digital Asset Management |last=Austerberry |first=D. |publisher=CRC Press |pages=27–28 |year=2012 |isbn=9781136033629 |access-date=19 May 2018}}</ref> or can integrate with workflow management tools.<ref name="FletcherWorkflow03" /> There are different types of workflow. Usage depends on the environment to which the electronic document management system (EDMS) is applied. 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, 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 act in real time, allowing multiple users to view and modify (or markup) documents at the same time. The resulting document is comprehensive, including all users additions. Collaboration within document management systems means that the various markups by each individual user during the collaboration session are recorded, allowing document history to be monitored.<ref name="AusterberryDigital12-2">{{cite book |url=https://books.google.com/books?id=c5ncAwAAQBAJ&pg=PT38 |title=Digital Asset Management |last=Austerberry |first=D. |publisher=CRC Press |page=30 |year=2012 |isbn=9781136033629 |access-date=19 May 2018}}</ref>
|-
| '''[[Version control|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.<ref name="AusterberryDigital12-2" />
|-
| '''Searching''' || Searching finds documents and folders using template attributes or full text search. Documents can be searched using various attributes and document content.
|-
| '''Federated search''' || This refers to the capability to extend search capabilities to draw results from multiple sources, or from multiple DMSes within an enterprise.<ref name="WhiteEnterprise12">{{cite book |url=https://books.google.com/books?id=4M46PRgJmJYC&pg=PA73 |title=Enterprise Search |last=White |first=M. |publisher=O'Reilly Media, Inc |pages=73–74 |year=2012 |isbn=9781449330408 |access-date=19 May 2018}}</ref>
|-
| '''[[Publishing]]''' || Publishing a document involves the procedures of [[proofreading]], [[Peer review|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 [[International Organization for Standardization|ISO]] divisions of ICS 01.140.40 and 35.240.30 for further information.<ref name=pub>{{cite web
 |last        = International Organization for Standardization
 |title       = 01.140.40: Publishing
 |url         = http://www.iso.org/iso/products/standards/catalogue_ics_browse.htm?ICS1=01&ICS2=140&ICS3=40&
 |access-date  = 14 July 2008
 |url-status     = live
 |archive-url  = https://web.archive.org/web/20110606045311/http://www.iso.org/iso/products/standards/catalogue_ics_browse.htm?ICS1=01&ICS2=140&ICS3=40&
 |archive-date = 6 June 2011
}}</ref><ref name=itpub>{{cite web
 |last        = International Organization for Standardization
 |title       = 35.240.30: IT applications in information, documentation and publishing
 |url         = http://www.iso.org/iso/catalogue_ics_browse?ICS1=35&ICS2=240&ICS3=30&
 |access-date  = 14 July 2008
 |url-status     = live
 |archive-url  = https://web.archive.org/web/20110606045331/http://www.iso.org/iso/catalogue_ics_browse?ICS1=35&ICS2=240&ICS3=30&
 |archive-date = 6 June 2011
}}</ref>
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.<ref name=sdmv>{{cite web|last=OnSphere Corporation|title=SOP Document Management in a Validated Environments|url=http://www.avidoffice.com/docushare/dsweb/Get/Document-9101/Standard%20Operation%20Procedure%20(SOP)%20Document%20Management%20in%20Validated%20Environments.pdf|access-date=25 April 2011|archive-url=https://web.archive.org/web/20110904190514/http://www.avidoffice.com/docushare/dsweb/Get/Document-9101/Standard%20Operation%20Procedure%20%28SOP%29%20Document%20Management%20in%20Validated%20Environments.pdf|archive-date=4 September 2011|url-status=dead}}</ref>
|-
| '''Hard copy reproduction''' || Document/image reproduction is often necessary within a document management system, and its supported output devices and reproduction capabilities should be considered.<ref name="MeurantInto12-2">{{cite book |url=https://books.google.com/books?id=lzGGHLDERYIC&pg=PA16 |title=Introduction to Electronic Document Management Systems |last=Meurant |first=G. |publisher=Academic Press |page=16 |year=2012 |isbn=9780323140621 |access-date=19 May 2018}}</ref>
|}