Conversation
| normalized(){ | ||
| // normalized := has a name and is associated | ||
| const name = this.syncher.get('name'); | ||
| return name && this.associated() && this.completed(); |
There was a problem hiding this comment.
Not sure what 'completed' was supposed to indicate?
There was a problem hiding this comment.
associated true (entity/node only) => grounded
completed (any element / node / edge) => the user has finished specifying the element
E.g. an interaction doesn't have a grounding but it can still be completed by specifying it as phosphorylation.
|
Admin page examples for (top) unnormalized entity (blocks public status) (bottom) mixed organisms (warning) |
maxkfranz
left a comment
maxkfranz
left a comment
There was a problem hiding this comment.
Looks great.
Suggestion for future: A filter at the top for these flagged, problematic documents would be nice so you don't have to hunt for them.
I suppose a submitted/not-public would be the same, but it's not as clear.
Good point, there are some blocked (submitted) contributions that I never reviewed, missed. Add this to a few other admin features required, based on things I'm doing manually:
|
2 participants
Here I augment the admin/model to flag common entity-level issues:
Question: For convenience, I added an entity
normalizedmethod, but I can't recall what the difference is betweenassociatedandcompleted?Refs #1286, part 'c'