Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

backend-addons #17

Closed
linupi opened this issue Jan 23, 2023 · 2 comments · Fixed by #27
Closed

backend-addons #17

linupi opened this issue Jan 23, 2023 · 2 comments · Fixed by #27
Assignees

Comments

@linupi
Copy link
Contributor

linupi commented Jan 23, 2023

Additional endpoints needed:

@linupi
Copy link
Contributor Author

linupi commented Jan 23, 2023

look at options to add unique IDs to 'keys' in metadata shema (needed for update). E.g.

{
    _id: ObjectId('62a837d155adb3f37e5fb40e'),
    schema_name: 'calibration',
    schema_type: 'dataset',
    keys: [
        {
             _id: ObjectId('dgffdsgfsdgdfsg'),     <--- is it possilbe to insert _id on this level in Mongo?
            key_name: 'energy',
            type: 'number',
            required: true,
            scan_ref: false,
            changes_likely: true,
            unit: 'keV'
        },
        {
            key_name: 'sample_detector_distance',
            type: 'number',
            required: false,
            scan_ref: false,
            changes_likely: true,
            unit: null
        },
        {
            key_name: 'central_pixel_x',
            type: 'number',
            required: false,
            scan_ref: false,
            changes_likely: true,
            unit: null
        },
        {
            key_name: 'central_pixel_y',
            type: 'number',
            required: false,
            scan_ref: false,
            changes_likely: true,
            unit: null
        },
        {
            key_name: 'calibration_file',
            type: 'string',
            required: false,
            scan_ref: false,
            changes_likely: true,
            unit: null
        }
    ],
    fixed_value_entries: false
}

@linupi
Copy link
Contributor Author

linupi commented Feb 23, 2023

Idea:
add PUT /addons/metadata_schema_key that takes schema_name and key_name as arguments togehter with the key description so that it only works on in the focus of key

schema_name:'bla',
key_name:'sample_detector_distance',
update: {
            key_name: 'sample_detector_distance',
            type: 'number',
            required: false,
            scan_ref: false,
            changes_likely: true,
            unit: null
 },

add DELETE /addons/metadata_schema_key with payload

schema_name:'bla',
key_name:'sample_detector_distance',

@linupi linupi linked a pull request Apr 20, 2023 that will close this issue
linupi added a commit that referenced this issue Nov 30, 2023
…_initdb.d

Use seperate schema extension repo and initdb.d for demo data
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant