Home

Application Name	Developer	Made with	Rating	Last updated	Views	Installs
demo-dbs-iris This project provides a Docker container running an InterSystems IRIS database. The database includes multiple namespaces, each featuring demo datasets designed for exploring various scenarios, including data analysis, application prototyping, and testing.	A Andreas Schneider		5.0 (1)	23 Nov, 2025	517
PIQXL Gateway Data Quality Scorecard with Detailed Dashboard	J John Wilkinson		0.0 (0)	22 Nov, 2025	95
InterSystems Ideas Waiting to be Implemented Pull in all classes and tables called in a resource at export. I would like to see any utilized class, table, global variable, etc. that is utilized within a production component pulled into the export list when I export from that component. Right now, tables, XML message schemas, message classes, and others are not being pulled into the export list and it leads to missing classes when pushing components into production. It also requires a lot of extra documentation to be sure that all of the pieces I am building get moved as expected. V by Victoria Castillo 8 Votes 2 Comments Vote
Data Catalog A single solution to easily discover and access reliable data	P Paulo Taylor		0.0 (0)	24 Aug, 2022	478
iris-climate-change IRIS Climate Change, Data Sciences, Plotting and Visualization	Muhammad Waseem	Docker Python	5.0 (1)	15 Jul, 2022	624
Medical Datasets Easy to use 12 DataSets containing 43 tables	Muhammad Waseem	Docker IPM	4.5 (1)	15 Jan, 2022	831	50

demo-dbs-iris

This project provides a Docker container running an InterSystems IRIS database. The database includes multiple namespaces, each featuring demo datasets designed for exploring various scenarios, including data analysis, application prototyping, and testing.

A

Andreas Schneider

5.0 (1)

23 Nov, 2025

517

PIQXL Gateway

Data Quality Scorecard with Detailed Dashboard

J

John Wilkinson

0.0 (0)

22 Nov, 2025

95

InterSystems Ideas Waiting to be Implemented

Pull in all classes and tables called in a resource at export.

I would like to see any utilized class, table, global variable, etc. that is utilized within a production component pulled into the export list when I export from that component. Right now, tables, XML message schemas, message classes, and others are not being pulled into the export list and it leads to missing classes when pushing components into production. It also requires a lot of extra documentation to be sure that all of the pieces I am building get moved as expected.

V

by Victoria Castillo