Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Data element
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
{{Short description|Semantic representation of data}} {{Data transformation}} In [[metadata]], the term '''data element''' is an atomic unit of data that has precise meaning or precise semantics. A data element has: # An identification such as a [[data element name]] # A clear [[data element definition]] # One or more [[representation term]]s # Optional enumerated values [[Code (metadata)]] # A list of synonyms to data elements in other metadata registries [[Synonym ring]] Data elements usage can be discovered by inspection of [[software application]]s or application [[data file]]s through a process of manual or automated [[Application Discovery and Understanding]]. Once data elements are discovered they can be registered in a [[metadata registry]]. In [[telecommunications]], the term '''data element''' has the following components: #A named unit of [[data]] that, in some contexts, is considered indivisible and in other contexts may consist of data items. #A named [[identifier]] of each of the entities and their attributes that are represented in a [[database]]. #A basic unit of [[information]] built on standard structures having a unique meaning and distinct units or values. #In electronic record-keeping, a combination of characters or bytes referring to one separate item of information, such as name, [[Address (geography)|address]], or age. In the areas of [[databases]] and [[data systems]] more generally a data element is a concept forming part of a [[data model]]. As an element of data representation, a collection of data elements forms a [[data structure]].<ref>Beynon-Davies P. (2004). Database Systems 3rd Edition. Palgrave, Basingstoke, UK</ref> == In practice == In practice, data elements (fields, columns, attributes, etc.) are sometimes "overloaded", meaning a given data element will have multiple potential meanings. While a known bad practice, overloading is nevertheless a very real factor or barrier to understanding what a system is doing. ==See also== * [[Application Discovery and Understanding]] * [[Data element definition]] * [[Data dictionary]] * [[Data hierarchy]] * [[ISO/IEC 11179]] metadata registry specification * [[Metadata]] * [[Representation term]] * [[Universal Data Element Framework]] * [[Data collection system]] ==References== {{reflist}} *{{FS1037C}} *{{DODDIC}} == External links == * [https://web.archive.org/web/20050826195309/http://xml.gov/documents/in_progress/developersguide.pdf Federal XML Developer's Guide] * [http://isotc.iso.org/livelink/livelink/fetch/2000/2489/Ittf_Home/PubliclyAvailableStandards.htm ISO/IEC 11179 Standards] (see ISO/IEC 11179-3:2003 clause 3.3.36) {{DEFAULTSORT:Data Element}} [[Category:Metadata]] [[Category:Enterprise application integration]] {{database-stub}}
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)
Pages transcluded onto the current version of this page
(
help
)
:
Template:DODDIC
(
edit
)
Template:Data transformation
(
edit
)
Template:Database-stub
(
edit
)
Template:FS1037C
(
edit
)
Template:Reflist
(
edit
)
Template:Short description
(
edit
)