Operating system:: MS or cloud-transpar
Outlook version: M365
Email type or host: M365
Outlook version: M365
Email type or host: M365
Sorry if off topic, but Diane and community seem like the best group to ask.
TL;DR- Data as individual, manageable items versus data as elements within a document/file. e.g. Structured vs Unstructured? I just want to hear what is most common in the community.
When speaking to IT leadership, I want to discuss the pros and cons of data elements stored database-based applications versus being stored as structured text in Office documents. e.g. a SharePoint list versus a bulleted list or table in Word. Or JIRA issues versus an Excel list. So, regardless of the tool used, what generic terminology would you use to differentiate the database record type from the file's list item type?
My goal is to set the terminology straight as we discuss using a database tool with free-er text in many Office documents. The current issue relates to a $5M, 5yr IT project whose tasks, risks, decisions, results are stored in hundreds of Office documents in dozens of folders in a SharePoint library. The group is happy to now have one place to save their files, but spends tons of time consolidating similar data into one set every time a question comes up.
Thank you
TL;DR- Data as individual, manageable items versus data as elements within a document/file. e.g. Structured vs Unstructured? I just want to hear what is most common in the community.
When speaking to IT leadership, I want to discuss the pros and cons of data elements stored database-based applications versus being stored as structured text in Office documents. e.g. a SharePoint list versus a bulleted list or table in Word. Or JIRA issues versus an Excel list. So, regardless of the tool used, what generic terminology would you use to differentiate the database record type from the file's list item type?
My goal is to set the terminology straight as we discuss using a database tool with free-er text in many Office documents. The current issue relates to a $5M, 5yr IT project whose tasks, risks, decisions, results are stored in hundreds of Office documents in dozens of folders in a SharePoint library. The group is happy to now have one place to save their files, but spends tons of time consolidating similar data into one set every time a question comes up.
Thank you