Enabling or disabling notebook extensions by injecting user configuration at runtime

US2025383889A1 · US · A1

Patent metadata
FieldValue
Publication numberUS-2025383889-A1
Application numberUS-202519052798-A
CountryUS
Kind codeA1
Filing dateFeb 13, 2025
Priority dateJun 13, 2024
Publication dateDec 18, 2025
Grant date

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Techniques are described for enabling or disabling extensions at runtime. Instead of providing same user experience to customers, using techniques described herein, users of the notebook service can easily customize a JupyterLab experience by enabling or disabling UI extensions. This customization request is not limited to the UI only, customers can use an API to disable and or enable extensions.

First claim

Opening claim text (preview).

What is claimed is: 1 . A method to enable and disable extensions associated with a notebook service, the method comprising: receiving a request to initiate a notebook session associated with a user; determining one or more extensions to include in the notebook session; causing the notebook session to be initiated within a cloud computing environment; and causing the one or more extensions to be one or more of enabled or disabled within the notebook session. 2 . The method of claim 1 , wherein determining the one or more extensions to include in the notebook session comprises accessing a database that includes configurations of extensions of the notebook service for different customers of the notebook service. 3 . The method of claim 1 , further comprising: receiving a second request to initiate a second notebook session associated with a second user; determining one or more second extensions to include in the second notebook session; causing the second notebook session to be initiated within the cloud computing environment; and causing the one or more second extensions to be one or more of enabled or disabled. 4 . The method of claim 1 , wherein receiving the request comprises receiving the request from a user interface associated with a computing device external to the cloud computing environment. 5 . The method of claim 1 , wherein determining the one or more extensions to include in the notebook session comprises accessing configuration data associated with the user and generating a file that indicates the one or more extensions. 6 . The method of claim 5 , further comprising initiating a user interface on a web-based client that uses the file to cause the one or more extensions to be one or more of enabled or disabled. 7 . The method of claim 1 , wherein receiving the request comprises receiving the request at a notebook manager that is connected to a web program and a server configured to run JupyterLab. 8 . A system, comprising: a network that includes network devices; a data store that stores configuration data that specifies extensions to enable and/or disable within notebook sessions for a plurality of users; one or more processors; and non-transitory computer-readable medium storing a set of instructions, the set of instructions when executed by the one or more processors cause processing to be performed comprising: receiving a request to initiate a notebook session associated with a user; determining, based at least in part on the configuration data, one or more extensions to include in the notebook session; causing the notebook session to be initiated; and causing the one or more extensions to be one or more of enabled or disabled. 9 . The system of claim 8 , wherein determining the one or more extensions comprises accessing a database that includes configurations of extensions of a notebook service for different customers of the notebook service. 10 . The system of claim 8 , further comprising: receiving a second request to initiate a second notebook session associated with a second user; determining one or more second extensions to include in the second notebook session; causing the second notebook session to be initiated; and causing the one or more second extensions to be one or more of enabled or disabled. 11 . The system of claim 8 , wherein receiving the request comprises receiving the request from a user interface associated with the user of a cloud computing environment. 12 . The system of claim 8 , further comprising generating a file that indicates the one or more extensions to one or more of enable or disable. 13 . The system of claim 12 , further comprising initiating a user interface on a web-based client that uses the file to cause the one or more extensions to be one or more of enabled or disabled. 14 . The system of claim 8 , further comprising a notebook manager, and wherein receiving the request comprises receiving the request at the notebook manager that is connected to a web program and a server configured to run JupyterLab. 15 . A non-transitory computer-readable medium comprising instructions that when executed, cause one or more processors to perform operations including: receiving a request to initiate a notebook session associated with a user; determining one or more extensions to include in the notebook session; causing the notebook session to be initiated within a cloud computing environment; and causing the one or more extensions to be one or more of enabled or disabled. 16 . The computer-readable medium of claim 15 , wherein determining the one or more extensions to include in the notebook session comprises accessing a database that includes configurations of extensions of a notebook service for different customers of the notebook service. 17 . The computer-readable medium of claim 15 , further comprising: receiving a second request to initiate a second notebook session associated with a second user; determining one or more second extensions to include in the second notebook session; causing the second notebook session to be initiated within the cloud computing environment; and causing the one or more second extensions to be one or more of enabled or disabled. 18 . The computer-readable medium of claim 15 , wherein receiving the request comprises receiving the request from a user interface associated with the user of the cloud computing environment. 19 . The computer-readable medium of claim 15 , wherein determining the one or more extensions to include in the notebook session comprises accessing configuration data associated with the user and generating a file that indicates the one or more extensions to one or more of enable or disable. 20 . The computer-readable medium of claim 19 , further comprising initiating a user interface on a web-based client that uses the file to cause the one or more extensions to be one or more of enabled or disabled.

Assignees

Inventors

Classifications

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US2025383889A1 cover?
Techniques are described for enabling or disabling extensions at runtime. Instead of providing same user experience to customers, using techniques described herein, users of the notebook service can easily customize a JupyterLab experience by enabling or disabling UI extensions. This customization request is not limited to the UI only, customers can use an API to disable and or enable extensions.
Who is the assignee on this patent?
Oracle Int Corp
What technology area does this patent fall under?
Primary CPC classification G06F9/4451. Mapped technology areas include Physics.
When was this patent published?
Publication date Thu Dec 18 2025 00:00:00 GMT+0000 (Coordinated Universal Time) (A1). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).