{"id":1909,"date":"2024-02-21T07:34:26","date_gmt":"2024-02-21T07:34:26","guid":{"rendered":"https:\/\/itbac.eu\/books\/data-field-analysis\/"},"modified":"2025-02-28T13:41:31","modified_gmt":"2025-02-28T13:41:31","slug":"data-field-analysis","status":"publish","type":"page","link":"https:\/\/www.itbac.eu\/en\/books\/data-field-analysis\/","title":{"rendered":"Data field analysis"},"content":{"rendered":"\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

practical manual and checklist<\/h2>\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t
\n

During the course of an analyst’s work, it is surprisingly common to deal with data field analysis<\/i>.<\/p>\n

This is a term I have coined specifically for this particular book. Yet I am certain that anyone who has done IT systems analysis has either performed data field analysis\u2014or made rather arbitrary decisions about it, or left it for someone else to handle.<\/p>\n

Data field analysis is the analysis of the attributes of data objects across all levels of technicality.<\/p>\n<\/div>\n

\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t
\n\t\t\t\t
\n\t\t\t\t\t
1st draft<\/h6>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t\t
2nd draft<\/h6>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t\t
e-book <\/h6>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t\t
print<\/h6>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t\t
translation<\/h6>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t
complete<\/div>\t\t\t
\n\t\t\t\t<\/span>\n\t\t\t\t1<\/span>\n\t\t\t\tch<\/span>\n\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t
planned <\/div>\t\t\t
\n\t\t\t\t<\/span>\n\t\t\t\t32<\/span>\n\t\t\t\tch<\/span>\n\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t
A4 ready <\/div>\t\t\t
\n\t\t\t\t<\/span>\n\t\t\t\t0<\/span>\n\t\t\t\tp<\/span>\n\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t
words<\/div>\t\t\t
\n\t\t\t\t<\/span>\n\t\t\t\t10000<\/span>\n\t\t\t\t<\/span>\n\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

last edit: <\/span>
6.02.2024<\/span><\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t\t\t\t\t

on pause until the previous book is ready<\/span><\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

This is how Kaja Trees’<\/a> book begins, though it still requires a bit of content refinement before publication.<\/p>\n

The book describes what is happening in system analyst’s brain while they have to make decisions regarding data field naming, displaying, behavior etc. It contains a detailed description that one needs to consider during this process for different types of data fields and also delivers this thought process for some of the most common data fields specifically.<\/p>\n

The book helps Business, System and Data Analysts understand, how they are making those decisions, and make those decisions smarter in the future.<\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

04.01.2025 status<\/h3>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Currently, the writing of this book is on hold until the shorter planned book, Optimal Documentation: Useful, Cohesive, and Up-to-Date<\/a>, is ready. <\/p>\n

Nonetheless, I can assure you that I anticipate completing this book by the end of this year, even though it has been on hold for quite some time. <\/p>\n

A significant portion of the book has already been written, and it can be considered a second draft, as it already incorporates feedback from a content editor and test readers. I am a bit stuck on describing one of the more complex and common data objects\u2014location and everything associated with it. I definitely want to elaborate on this in the book, as well as describe file imports, provide some practical examples, and more. <\/p>\n

I will certainly keep you updated both here and through the mailing list below when I return to writing this book!<\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
<\/div>\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"

practical manual and checklist During the course of an analyst’s work, it is surprisingly common to deal with data field analysis. This […]<\/p>\n","protected":false},"author":3,"featured_media":0,"parent":1903,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"footnotes":""},"class_list":["post-1909","page","type-page","status-publish","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.itbac.eu\/en\/wp-json\/wp\/v2\/pages\/1909","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.itbac.eu\/en\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.itbac.eu\/en\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.itbac.eu\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.itbac.eu\/en\/wp-json\/wp\/v2\/comments?post=1909"}],"version-history":[{"count":1,"href":"https:\/\/www.itbac.eu\/en\/wp-json\/wp\/v2\/pages\/1909\/revisions"}],"predecessor-version":[{"id":1910,"href":"https:\/\/www.itbac.eu\/en\/wp-json\/wp\/v2\/pages\/1909\/revisions\/1910"}],"up":[{"embeddable":true,"href":"https:\/\/www.itbac.eu\/en\/wp-json\/wp\/v2\/pages\/1903"}],"wp:attachment":[{"href":"https:\/\/www.itbac.eu\/en\/wp-json\/wp\/v2\/media?parent=1909"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}