If one of your packages on OEX receives a review you get notified by OEX only own YOUR package.   
The rating reflects the experience of the reviewer with the status found at the time of review.   
It is kind of a snapshot and might have changed meanwhile.   
Reviews by other members of the community are marked by * in the last column.

I also placed a bunch of Pull Requests on Github when I found a problem I could fix.    
Some were accepted and merged, and some were just ignored.     
So if you did a major change and expect a changed review just let me know.

If one of your packages on OEX receives a review you get notified by OEX only own YOUR package.   
The rating reflects the experience of the reviewer with the status found at the time of review.   
It is kind of a snapshot and might have changed meanwhile.   
Reviews by other members of the community are marked by * in the last column.

I also placed a bunch of Pull Requests on Github when I found a problem I could fix.    
Some were accepted and merged, and some were just ignored.     
So if you did a major change and expect a changed review just let me know.

I produce my monthly Review Report on OEX packages now for 18 months.
These are a view figures and some comments:

• Total packages checked = 669
• Packages tested and reviewed by myself = 294
• Packages reviewed by other community contributors = 41  
• Packages without review = 334
  • These are packages that promote partner products
  • or are mostly not available with a Docker set-up
  • or require resources unavailable to me (e.g. license keys)  
  • or I simply didn't understand the subject  (e.g most Health* subjects)

If one of your packages on OEX receives a review you get notified by OEX only own YOUR package.   
The rating reflects the experience of the reviewer with the status found at the time of review.   
It is kind of a snapshot and might have changed meanwhile.   
Reviews by other members of the community are marked by * in the last column.

I also placed a bunch of Pull Requests on Github when I found a problem I could fix.    
Some were accepted and merged, and some were just ignored.     
So if you did a major change and expect a changed review just let me know.

If one of your packages on OEX receives a review you get notified by OEX only own YOUR package.   
The rating reflects the experience of the reviewer with the status found at the time of review.   
It is kind of a snapshot and might have changed meanwhile.   
Reviews by other members of the community are marked by * in the last column.

I also placed a bunch of Pull Requests on Github when I found a problem I could fix.    
Some were accepted and merged, and some were just ignored.     
So if you did a major change and expect a changed review just let me know.

I just met a personal challenge translating my article to French.
Tough I had to learn it at school and could read and understand
famous literature (Sartre, Molière, Mauriac, Proust, Saint-Exupéry, Anouilh, ...) 
I missed the specific terms used with ISC technology.
Thanks to @Lorenzo Scalese my errors were corrected.
But no dictionary was able to answer. 
Especially as English is gender-neutral the individual gender in other languages is just undefined.
QUESTION:
- Is there anywhere a Dictionary in ISC to cover this issue?
What I'm looking for may look like this table

If one of your packages on OEX receives a review you get notified by OEX only own YOUR package.   
The rating reflects the experience of the reviewer with the status found at the time of review.   
It is kind of a snapshot and might have changed meanwhile.   
Reviews by other members of the community are marked by * in the last column.

I also placed a bunch of Pull Requests on Github when I found a problem I could fix.    
Some were accepted and merged, and some were just ignored.     
So if you did a major change and expect a changed review just let me know.

My major interest is  Working with Globals in Embedded Python.
So I checked the available official documentation.

#1 Introduction to Globals
an attempt of a generic description of what a global is. Pointing to

#2 A Closer Look at ObjectScript
But where is Embedded Python ?
Way down you see

#3 Embedded Python

The 24th contest was dominated by already well know winners
+ 3 new winning contributors GROWTH: 8,6%
Participation by my 5 regions:

as: 1, br: 4, eu: 4+1new,  us: 1+2new,  ru: 5,   total:18   
With is distribution:  

This results over all 24 contests into:

The Top 6 performing winners:

If one of your packages on OEX receives a review you get notified by OEX only own YOUR package.   
The rating reflects the experience of the reviewer with the status found at the time of review.   
It is kind of a snapshot and might have changed meanwhile.   
Reviews by other members of the community are marked by * in the last column.

I also placed a bunch of Pull Requests on Github when I found a problem I could fix.    
Some were accepted and merged, and some were just ignored.     
So if you did a major change and expect a changed review just let me know.

ZPM is a great tool.
You can compose a large WebApplication following the existing examples.   
But differently, to Classes, Routines, Macros, or Globals I found no direct way     
to deploy a few additional CSP pages directly into an existing Namespace     
without touching the existing content.

A side issue was to find a solution that is independent of WIN or Linux directories.

My solution acts in 2 steps

1. Loading the CSP sources from ZPM
2. Moving them into the Namespace and compiling them.

#1 is a ZPM default and uses an intermediate CSP_directory
#2 is covered by $System.OBJ.ImportDir()

There is a popular package "WebTerminal". It is excellent in most situations.
Except:

I'm sure you have met this situation:

• There is a bug in a System that you can't reproduce yourself locally
• You need to run a few lines in the affected instance
• You get full access to System Management Portal
• But there is just  no terminal, nor console, nor access with Studio, Atelier or VSCode
• How to run your few lines for testing ???

In March'22 you may have seen an invitation to 
Share a Demo of Your Open Exchange Application
The service behind it - InterSystems Online Demo Server (ODS) - is not something new

I saw it first during InterSystems Developer Tools Contest in March '21 as Bonus points.
Meanwhile, it became a fixed Bonus item over the later contests. Also the actual #24. 
And by today we see already 80 packages listed in OEX as available on ODS.

To me  the advantage for developers is apparent:

Implementation

• B is the Winner Table: It holds the region and a numeric as ID. Short name is left empty for privacy protection in this Demo
• A is the table of all contests with dates
• X,C  are the arrays of prizes. They are projected as SQL tables.   When assigned they refer to 1 winner

User guide

Start the demo in Docker from IRIS console or in Webterminal

USER>do ##class(dc.rcc.Main).Menue()

You jump on top of fresh page

Welcome to OEX Contest Statistics

Select Contests, Prizes, Winners, Assign, Statistics, eXit (C,P,W,A,S,X) :

M:N Relationship is a recurring object of my interest for a long time.
So the subject turns up with me repeatedly.
For this article, I found a nice example with TWO  separate M:N relationships. Some M:N².

It is not pure fiction but taken from a closer view of OEX Contests that we run on a regular base.

If one of your packages on OEX receives a review you get notified by OEX only own YOUR package.   
The rating reflects the experience of the reviewer with the status found at the time of review.   
It is kind of a snapshot and might have changed meanwhile.   
Reviews by other members of the community are marked by * in the last column.

I also placed a bunch of Pull Requests on Github when I found a problem I could fix.    
Some were accepted and merged, and some were just ignored.     
So if you did a major change and expect a changed review just let me know. 

This package offers a utility to export an XLarge Global into a JSON object file and to show
or import it again. In a previous example, this all was processed in memory. But if this is a
large Global you may either experience <MAXSTRING> or an <STORE>  error
if the generated JSON structure exceeds available memory.
 

Academic refers to the structure created.

I have a rather simplistic JSON Object of this structure: 

{"id":<someid>,"value":<some string>,"details": 
 [{"id":<someid>,"value":<some string>,"details": 
  [{"id":<someid>,"value":<some string>,"details":  
   [{"id":<someid>,"value"}
   ,{"id":<someid>,"value"} 
   ,{"id":<someid>,"value"} ]
  ,[{"id":<someid>,"value":<some string>,"details":  
     [{"id":<someid>,"value"}
    ,{"id":<someid>,"value"} ] ]
 ,{"id":<someid>,"value":<some string>} ] } 
   

If one of your packages on OEX receives a review you get notified by OEX only own YOUR package.   
The rating reflects the experience of the reviewer with the status found at the time of review.   
It is kind of a snapshot and might have changed meanwhile.   
So if you did a major change and expect a changed review just let me know. 
Reviews by other members of the community are marked by * in the last column

This example demonstrates the difference you may experience when you write to
Gllobals directly from Embedded Python compared to native ObjectScript.

To make this demo useful I start 2 background jobs that simply write sequentially
to a dedicated global. A common control method signals for a synchronous start.
Similar a common stop & view interrupts data feeding.

That's the principle process:

It sounds strange though it's embarrassing.

I have a class with ClassMethods written in ISOS and Embedded Python.

The ClassMethods written in ISOS start in the Background as usual. No problems

But my 

ClassMethod setPy() [ Language = python ]
{
import iris, datetime, time
- - -

Just fails the JOB command with (even 15 sec) timeout and $ZC=0
This is not funny
My actual workaround:
I created a ClassMethod in ISOS, that does an elegant JobStart
and this ClassMethod only runs the Embedded Python ClassMethod.
I'm not amused and hope there is just an undocumented/unknown param missing

You may have seen my series of articles on GlobalToJSON closing with Embedded Python.
And to me, Embedded means inside a Class and not PEX or other external variants.
The first variants showed that ePy is not an ultimate requirement. ISOS/COS may do it as well.
Here I try to position ePy inside IRIS.

In my article I described the work using iris.gref .
As the official documetation is rather slim on the subject it was necessary to dig into it.
Using the power of Python I was able to detect what I needed but was hidden.
I decided to share this with you. pydoc did the magic. 

If one of your packages on OEX receives a review you get notified by OEX only own YOUR package.  The rating reflects the experience of the reviewer with the status found at the time of review.  It is kind of a snapshot and might have changed meanwhile.   
New with this edition:
Reviews by other members of the community are marked by * in the last column.

This package was triggered by the extra bonus points in the contest for writing the example
in embedded Python only.  Therefore PURE

I will give you some additional information on my first embedded Python package.
it is written as a mix of python and ObjectScript to take the best of both worlds.

I have created a package to export a Global into JSON object file and to re-create it by reloading from this file   
embeddedPython refers to the new available technologies. It should be understood as a learning exercise of 
how to handle the language interfaces. Only Global nodes containing data are presented in the generated JSON file.
Differently from the previous example, this one is using embedded Python only, no ObjectScript. Therefore PURE

I have created a package to export a Global into JSON object file and to re-create it by reloading from this file   
embeddedPython refers to the new available technologies. It should be understood as a learning exercise of 
how to handle the language interfaces. Only Global nodes containing data are presented in the generated JSON file.

If one of your packages on OEX receives a review you get notified by OEX only on YOUR package.
It reflects my experience with the status I found at the time of my review.
It is kind of a snapshot and might have changed meanwhile.