Skip to content

Section 1.1 The KG paradigm shit --> internal analysis  #3

Description

@msesboue

Today we tend to keep each and every piece of data "just in case". Doesn't it make the "internal data analysis" you mention in section 1.1 (page 3) always harder?

  • Do you have a method or "rule of thumb" to decide on what data we should keep or not?
  • Same question when scoping a KG project?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions