What's New in Grooper 2022: Difference between revisions
Dgreenwood (talk | contribs) |
Dgreenwood (talk | contribs) |
||
| Line 10: | Line 10: | ||
== Projects == | == Projects == | ||
'''Projects''' are a new object in Grooper version 2022. This fundamentally changes the Grooper Node Tree's organization for the better. A '''Project''' allows for simplified organization of Grooper assets, such as '''Content Models''', '''Batch Processes''', extractors and profiles, related to a single use case (or "project") into a single location in the Node Tree. No longer do you need to navigate to different locations in the Node Tree to access each of these components. Instead, you can organize all these disparate objects into a single, unified '''Project'''. | |||
This architecture also works to maintain reference integrity for objects referenced across multiple '''Batch Processes''' and '''Content Models'''. When an object refences another object and that object references a third object and that object references yet another, you can form a complicated web of "reference spaghetti", creating dependencies which you may or may not intend, particularly when (either intentionally or accidentally) creating cross references across multiple '''Content Models'''. This can cause problems down the road when importing or exporting Grooper objects, publishing Grooper objects to another Grooper Repository, or troubleshooting. The new Projects architecture makes establishing and maintaining references much more explicit and intentional in order to better protect from a mess of interconnected references that is difficult to unravel. | |||
== Web Review == | == Web Review == | ||
Revision as of 10:23, 15 February 2022
Welcome to Grooper 2022!
|
Grooper version 2022 is here! Below you will find brief descriptions on new and/or changed features. When available, follow any links to extended articles on a topic. |
Projects
Projects are a new object in Grooper version 2022. This fundamentally changes the Grooper Node Tree's organization for the better. A Project allows for simplified organization of Grooper assets, such as Content Models, Batch Processes, extractors and profiles, related to a single use case (or "project") into a single location in the Node Tree. No longer do you need to navigate to different locations in the Node Tree to access each of these components. Instead, you can organize all these disparate objects into a single, unified Project.
This architecture also works to maintain reference integrity for objects referenced across multiple Batch Processes and Content Models. When an object refences another object and that object references a third object and that object references yet another, you can form a complicated web of "reference spaghetti", creating dependencies which you may or may not intend, particularly when (either intentionally or accidentally) creating cross references across multiple Content Models. This can cause problems down the road when importing or exporting Grooper objects, publishing Grooper objects to another Grooper Repository, or troubleshooting. The new Projects architecture makes establishing and maintaining references much more explicit and intentional in order to better protect from a mess of interconnected references that is difficult to unravel.
Web Review
Review Queues
A new replacement for access control lists to make managing security access much easier.