Masader is a metadata catalog for Arabic NLP datasets, providing structured information about over 100 datasets including their tasks, dialects, sources, volumes, and licensing. The repository combines a Jekyll-based static site with a modular JavaScript frontend to enable dataset discovery through search, filtering, statistics visualization, and a natural language chatbot interface. While the core asset is the dataset metadata (JSON files in /datasets/), the web interface and associated tools (annotation, migration, validation scripts) form an application layer that makes the catalog usable and maintainable. The system supports dataset exploration via faceted search, demographic charts, and embedding-based clustering, with a chatbot for conversational queries. Metadata is kept up-to-date through migration scripts that handle schema evolution and validation checks that ensure consistency with external sources like venue links and volume totals.
Amundsen is an archived data discovery and metadata management platform. The codebase is structured as a multi-service monorepo: a Flask+React frontend, a Flask metadata service backed by graph databases, a Flask Elasticsearch search service, a shared common models library, and the databuilder ETL framework. In production it ingests metadata from databases, warehouses, dashboards, and feature stores through pluggable extractor/transformer/loader/publisher pipelines, publishes it to Neo4j/Neptune/Atlas/MySQL and Elasticsearch, and exposes search, table/dashboard/feature details, lineage, tags, badges, owners, quality checks, and previews through REST APIs and a React/Redux UI. The databuilder component is a genuinely library-quality ETL framework with clean interfaces, serialization abstractions for multiple backends, and a large collection of source-specific connectors. The metadata and search services are conventional Flask REST APIs, while the frontend is a large React application organized around Redux ducks and Redux-Saga async flows. Because of its data-ingestion components, the repository has a hybrid character, but the dominant character is an application platform rather than a data-research project. The project has been archived and shows significant technical drift: it pins Elasticsearch 7.13, Neo4j 4.4, and Node 12 (EOL), contains deprecated preview and search-publisher paths, has duplicated logic across services, and receives no active dependency or security updates. It remains useful as a reference architecture and as a source of extractable engineering patterns, but it is not a safe choice for new production deployments without a fork and substantial modernization.