|
1 | | -[](https://creativecommons.org/licenses/by/4.0/) |
2 | | -[](https://github.com/dimitri-yatsenko/datajoint-book/actions/workflows/main.yml) |
| 1 | +# ⚠️ Repository Archived |
3 | 2 |
|
| 3 | +> **This repository has been archived and is no longer maintained.** |
| 4 | +> |
| 5 | +> **Content has moved to the unified DataJoint documentation:** |
| 6 | +> |
| 7 | +> 🔗 **https://docs.datajoint.com** |
4 | 8 |
|
5 | | -# License |
| 9 | +--- |
6 | 10 |
|
7 | | -© DataJoint Inc., 2024-2025, All rights reserved. |
| 11 | +## Where to Find Content |
8 | 12 |
|
9 | | -This work is licensed under the [CC BY 4.0 License](LICENSE.md). |
10 | | -You may: |
11 | | -* share the content in any medium or format |
12 | | -* adapt, remix, transform, and build upon the material for any purpose |
13 | | - |
14 | | -Provided that you: |
15 | | -* give appropriate credit and indicate if changes were made |
16 | | - |
17 | | - |
18 | | -# DataJoint Book |
19 | | - |
20 | | -Welcome to the [DataJoint Book](https://dimitri-yatsenko.github.io/datajoint-book), a comprehensive |
21 | | -introduction to relational database programming in the context of scientific computing and data science. |
22 | | - |
23 | | -This book is built as an **executable book**, following the principles of the [Executable Books Project](https://executablebooks.org/en/latest/), an international collaboration to build open source tools that facilitate publishing computational narratives using the Jupyter ecosystem. |
24 | | - |
25 | | -The book is authored using [MyST Markdown](https://mystmd.org/) (Markedly Structured Text), an extensible, semantic, and community-driven flavor of markdown designed for scientific and computational narratives. MyST enables us to: |
| 13 | +All content from the DataJoint Book has been integrated into the unified documentation for DataJoint 2.0+: |
26 | 14 |
|
27 | | -- Write rich, publication-quality content with enhanced markdown syntax |
28 | | -- Embed executable code cells and computational outputs directly in the documentation |
29 | | -- Generate interactive web pages and other output formats from the same source |
30 | | -- Maintain a single source of truth for documentation, examples, and executable content |
| 15 | +| Book Content | New Location | |
| 16 | +|--------------|--------------| |
| 17 | +| **Concepts & Theory** | [Explanation](https://docs.datajoint.com/explanation/) | |
| 18 | +| Relational Workflow Model | [Relational Workflow Model](https://docs.datajoint.com/explanation/relational-workflow-model/) | |
| 19 | +| Data Pipelines | [Data Pipelines](https://docs.datajoint.com/explanation/data-pipelines/) | |
| 20 | +| Data Model | [Data Model](https://docs.datajoint.com/explanation/#data-model) | |
| 21 | +| Query Algebra | [Query Algebra](https://docs.datajoint.com/explanation/query-algebra/) | |
| 22 | +| Type System | [Type System](https://docs.datajoint.com/explanation/type-system/) | |
| 23 | +| **Hands-On Learning** | [Tutorials](https://docs.datajoint.com/tutorials/) | |
| 24 | +| Getting Started | [First Pipeline](https://docs.datajoint.com/tutorials/basics/01-first-pipeline/) | |
| 25 | +| **Practical Guides** | [How-To Guides](https://docs.datajoint.com/how-to/) | |
| 26 | +| **API Reference** | [Reference](https://docs.datajoint.com/reference/) | |
31 | 27 |
|
32 | | -This approach ensures that all code examples in the book are tested, up-to-date, and can be run directly by readers, bridging the gap between documentation and hands-on learning. |
| 28 | +## New Documentation Structure |
33 | 29 |
|
34 | | -## Running the Book with Dev Containers |
| 30 | +The DataJoint documentation now follows the [Diátaxis](https://diataxis.fr/) framework, providing better organization: |
35 | 31 |
|
36 | | -This repository includes a **Dev Container** (Development Container) configuration that provides a pre-configured development environment with all necessary dependencies, tools, and extensions already set up. This eliminates the need to manually install Python, DataJoint, MyST, and other required packages on your local machine. |
| 32 | +- **[Explanation](https://docs.datajoint.com/explanation/)** — Conceptual understanding (replaces Book theory sections) |
| 33 | +- **[Tutorials](https://docs.datajoint.com/tutorials/)** — Learn by building (replaces Book examples) |
| 34 | +- **[How-To Guides](https://docs.datajoint.com/how-to/)** — Task-oriented guides |
| 35 | +- **[Reference](https://docs.datajoint.com/reference/)** — API and specifications |
37 | 36 |
|
38 | | -### What is a Dev Container? |
| 37 | +## What's Improved |
39 | 38 |
|
40 | | -A Dev Container is a Docker-based development environment that runs inside a container but integrates seamlessly with your code editor (like Visual Studio Code or GitHub Codespaces). It ensures that everyone working on the book has an identical, reproducible environment, regardless of their operating system or local setup. |
| 39 | +✅ **Updated for DataJoint 2.0** — All content reflects the latest features and APIs |
| 40 | +✅ **Executable notebooks** — Interactive Jupyter notebooks with runnable code |
| 41 | +✅ **Better organization** — Diátaxis framework for clearer navigation |
| 42 | +✅ **Expanded content** — More domain-specific examples and use cases |
| 43 | +✅ **Search functionality** — Full-text search across all documentation |
| 44 | +✅ **Version indicators** — Clear markers for feature versions |
41 | 45 |
|
42 | | -### How to Use the Dev Container |
| 46 | +## Getting Started |
43 | 47 |
|
44 | | -**Option 1: Using Visual Studio Code (Local)** |
| 48 | +1. **Learn concepts:** Visit [Explanation](https://docs.datajoint.com/explanation/) |
| 49 | +2. **Build pipelines:** Try [Tutorials](https://docs.datajoint.com/tutorials/) |
| 50 | +3. **Solve problems:** Check [How-To Guides](https://docs.datajoint.com/how-to/) |
| 51 | +4. **Look up details:** Use [Reference](https://docs.datajoint.com/reference/) |
45 | 52 |
|
46 | | -1. Install [Docker Desktop](https://www.docker.com/products/docker-desktop) on your machine |
47 | | -2. Install [Visual Studio Code](https://code.visualstudio.com/) |
48 | | -3. Install the [Dev Containers extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) in VS Code |
49 | | -4. Clone this repository and open it in VS Code |
50 | | -5. When prompted, click "Reopen in Container" (or use Command Palette: `Dev Containers: Reopen in Container`) |
51 | | -6. VS Code will build the container and reload the workspace inside it |
| 53 | +## Migration to DataJoint 2.0 |
52 | 54 |
|
53 | | -**Option 2: Using GitHub Codespaces (Cloud)** |
| 55 | +If you're using DataJoint 0.14.x or earlier: |
54 | 56 |
|
55 | | -1. Navigate to this repository on GitHub |
56 | | -2. Click the green "Code" button |
57 | | -3. Select the "Codespaces" tab |
58 | | -4. Click "Create codespace on main" |
59 | | -5. GitHub will launch a cloud-based VS Code environment with the Dev Container already running |
| 57 | +📖 See the [Migration Guide](https://docs.datajoint.com/how-to/migrate-to-v20/) |
60 | 58 |
|
61 | | -Once inside the Dev Container, you have access to all tools needed to build, edit, and execute the book's content, including Jupyter notebooks, Python with DataJoint, and MyST build tools. |
| 59 | +For pre-2.0 documentation, visit [datajoint.github.io/datajoint-python](https://datajoint.github.io/datajoint-python). |
62 | 60 |
|
| 61 | +## Contributing |
63 | 62 |
|
64 | | -# Building and Deployment |
| 63 | +Contributions now go through the unified documentation repository: |
65 | 64 |
|
66 | | -Once you're working inside the Dev Container (see above), you can build and preview the book locally. |
| 65 | +- **Documentation:** [github.com/datajoint/datajoint-docs](https://github.com/datajoint/datajoint-docs) |
| 66 | +- **Contributing Guide:** [docs.datajoint.com/about/contributing](https://docs.datajoint.com/about/contributing/) |
| 67 | +- **Discussion:** [GitHub Discussions](https://github.com/datajoint/datajoint-python/discussions) |
67 | 68 |
|
68 | | -### Building the Book |
| 69 | +## License |
69 | 70 |
|
70 | | -The MyST static site deployment instructions are provided here: https://mystmd.org/guide/deployment |
| 71 | +© DataJoint Inc., 2024-2026, All rights reserved. |
71 | 72 |
|
72 | | -To build and serve the book locally: |
73 | | - |
74 | | -```shell |
75 | | -$ cd book |
76 | | -$ myst build --html |
77 | | -$ npx serve _build/html |
78 | | -``` |
79 | | - |
80 | | -This will: |
81 | | -1. Build the static HTML site from the MyST markdown and Jupyter notebook sources |
82 | | -2. Start a local web server (typically at `http://localhost:3000`) |
83 | | -3. Allow you to preview the book in your browser exactly as it will appear when deployed |
84 | | - |
85 | | -### Automatic Deployment |
86 | | - |
87 | | -The book is **automatically published** to [https://dimitri-yatsenko.github.io/datajoint-book](https://dimitri-yatsenko.github.io/datajoint-book) using GitHub Actions. |
88 | | - |
89 | | -Every time changes are pushed to the `main` branch, a GitHub Actions workflow: |
90 | | -1. Builds the book using MyST |
91 | | -2. Deploys the generated HTML to GitHub Pages |
92 | | -3. Makes the updated book immediately available online |
93 | | - |
94 | | -You can monitor the build and deployment status via the badge at the top of this README or by viewing the [Actions tab](https://github.com/datajoint/datajoint-book/actions) in the repository. This automated CI/CD pipeline ensures that the published version always reflects the latest content in the repository. |
| 73 | +This work is licensed under the [CC BY 4.0 License](LICENSE.md). |
| 74 | +You may: |
| 75 | +* share the content in any medium or format |
| 76 | +* adapt, remix, transform, and build upon the material for any purpose |
95 | 77 |
|
96 | | -### Manual Workflow Execution |
| 78 | +Provided that you: |
| 79 | +* give appropriate credit and indicate if changes were made |
97 | 80 |
|
98 | | -You can also manually trigger the "Build and Deploy DataJoint Book" workflow from the GitHub Actions interface: |
| 81 | +## Support |
99 | 82 |
|
100 | | -1. Navigate to the [Actions tab](https://github.com/datajoint/datajoint-book/actions) in the repository |
101 | | -2. Select the "Build and Deploy DataJoint Book" workflow from the left sidebar |
102 | | -3. Click the "Run workflow" button (on the right side) |
103 | | -4. Select the branch you want to run the workflow on (typically `main`) |
104 | | -5. Click "Run workflow" to start the build and deployment process |
| 83 | +- **Documentation:** https://docs.datajoint.com |
| 84 | +- **Community:** [GitHub Discussions](https://github.com/datajoint/datajoint-python/discussions) |
| 85 | +- **Issues:** [datajoint-docs issues](https://github.com/datajoint/datajoint-docs/issues) |
| 86 | +- **Email:** support@datajoint.com |
105 | 87 |
|
106 | | -This is useful when you want to rebuild and redeploy the book without making a new commit, or when testing workflow changes on a feature branch. |
| 88 | +--- |
107 | 89 |
|
108 | | -# Contributions |
109 | | -We welcome and appreciate your contributions to this book, whether as a reviewer or as a contributor. |
110 | | -All contributions will be gratefully acknowledged. |
111 | | -You may suggest modifications by submitting an issue in the main [GitHub repository](https://github.com/dimitri-yatsenko/datajoint-book) for this book. |
112 | | -For more substrantial contributions and collaborations, including co-authorship and publications, please contact Dimitri Yatsenko. |
| 90 | +**Last Updated:** January 2026 |
| 91 | +**Archive Date:** January 2026 |
0 commit comments