Feature #3769

Store metadata after an image registration

Added by Stavros Sachtouris almost 11 years ago. Updated over 10 years ago.

Status:Closed Start date:05/20/2013
Priority:High Due date:05/21/2013
Assignee:Stavros Sachtouris % Done:

100%

Category:kamaki Spent time: 9.00 hours
Target version:v0.9 Estimated time:8.00 hours

Description

Changes to image-register:

  • Store all metadata as a JSON-formated file on the remote location "next" to the image file. * Let user avoid writting the metadata file with the --no-metafile-upload runtime arg * meta file is stored iff the image is registered succesfully
  • Remote meta file path will be <image file path>.meta * If meta file already exists, abort image registration * let user force registration / overwrite meta with w. a -f runtime arg
  • Optionally load metadata from a local meta file, json-formated
  • Can introduce metadata from file AND runtime args (-p) simultaneously. Runtime args have higher priority

Related issues

related to ./kamaki - Feature #3797: Enrich image register meta record format Closed 05/23/2013 05/23/2013

Associated revisions

Revision 623a4ceb
Added by Stavros Sachtouris almost 11 years ago

Optionaly load images properties from file

Refs: #3769

Revision 00336c85
Added by Stavros Sachtouris almost 11 years ago

Store image properties after image registration

Log of changes:
- Properties are stored in a remote file on Pithos+
- File name is <image-file>.meta
- Feature can be switched off with --no-property-file-upload
- If remote property file exists, registration is aborted
- If remote property file exists, force with f, --fforce-upload-property-file
Location is given as container:path
- User id can be aquired internaly with an astakos call

Refs: #3769, #3778

Revision f7a37648
Added by Stavros Sachtouris almost 11 years ago

Make sure registered properties are unique

Refs: #3769

Revision c4aefeaf
Added by Stavros Sachtouris almost 11 years ago

Update and enrich error messages in image register

Parse ivalid property file and guide users to correct it
Guide users to pass valid container:path parameters

Refs:#3769

History

#1 Updated by Stavros Sachtouris almost 11 years ago

  • % Done changed from 0 to 40

#2 Updated by Stavros Sachtouris almost 11 years ago

  • % Done changed from 40 to 90

#3 Updated by Stavros Sachtouris almost 11 years ago

  • Status changed from Assigned to Resolved
  • % Done changed from 90 to 100

#4 Updated by Stavros Sachtouris over 10 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF