Talk:Data Model (Node Type)

From Grooper Wiki

Reanna Patton 11/19/2025

  • Under "What is a Data Model", "data fields" needs to be capitalized. Does a Database Lookup need to be capitalized? Calculated Field Expression?
    • Devon 11/19/2025: Capitalized Data Fields and Database Lookup. I went ahead and capitalized the "Field Expression" portion of "calculated Field Expression." Searching the Grooper wiki didn't turn anything up, so I'll leave what I've done and dig a bit deeper on that one.
  • "Data context can be critical to build the Data Type and Field Class extractors to populate a Data Model." I'm not sure what this means. I'm not sure that I would reference the Data Context article at this point as it doesn't seem super relevant.
    • Devon 11/19/2025: Deleted the quoted line and put in something simpler that drives hom the importance of having a Data Model in the first place.
  • Under "Data Models in Grooper" I would emphasize that the Data Model is a container that holds all Data Elements that are configured for extraction.
    • Devon 11/20/2025: Done.
  • Specifically what are you trying to show in your first screenshot. There are no arrows to indicate any specific part of the screenshot. It's not clear what you're trying to show.
  • Under "Inheritance and overrides" some objects need to be capitalized like Document Type.
    • Devon 11/20/2025: fixed
  • Under "Creating a Data Model" the first bullet point should probably not be a numbered bullet point, but rather a header leading into the numbered steps.
    • Devon 11/20/2025: fixed
  • "3. Select the Content Type - Create Data Model command." should that be just select the "Create Data Model" command?
    • Devon 11/20/2025: Yes. Yes it should be. Thanks for catching that, it's fixed now.
  • "To use inheritance, create child Data Models under a parent and override properties as needed." what does this mean? Create child Data Models? Under what? Data Models can only be added to Content Types to my understanding, so that's the only thing they can be children of.
  • I would put the instructions to adding multiple child objects as a separate set of instructions.
  • 1st supademo
    • The AI voice for the first slide needs to be fixed.
    • 6th or 7th slide, comma needs to be a period.
    • The slide where you Add Multiple Items and are selecting what Data Element you want to add, the text box overlaps with the above orange box.
  • 2nd supademo
    • 2nd slide doesn't have back and forth arrows.
    • Slide that says "Our Data Field is now added a child of the Data Model" should that be "Our Data Field is now added as a child of the Data Model"? (Both in text and AI)
    • Slide where you go to the Tester tab, arrows are on both text boxes instead of just one. Also, I think DD/DD/YYYY is supposed to be MM/DD/YYYY.
    • For this supademo, I don't think you really need to go all in on how to set up the extractor. Not necessarily bad that you did, just a little overkill imo. Could be simplified.
    • One one slide you have 4 text boxes. Looks like other slides have 3 text boxes. I think we said that we were only doing two text boxes per slide.
    • "Testing on the Data Model gives the same result, as the child object feeds the data up to the parent" doesn't need a comma.
Retrieved from "https://wiki.grooper.com/index.php?title=Talk:Data_Model_(Node_Type)&oldid=31808"