Implemented Metadata Definition UI

[arunapa]

[longshuicy]

I got a 422 error when posting definition:

Comparing your post body with the examples:

1. the context field should have another layer with the name of the definition as the key
2. you are missing the "name" of the definition, e.g. DOI at the root level

{
   "metadataName":"doi",
   "metadataDescription":"doi",
   "context":"https://schema.org/doi",
   "fields":[
      {
         "name":"doi",
         "list":false,
         "widgetType":"TextField",
         "config":{
            "type":"str",
            "options":""
         },
         "required":true
      }
   ]
}

vs

{
    "name" : "DOI",
    "description" : "Digital object identifier",
    "context" : {
        "doi" : "https://schema.org/DigitalDocument"
    },
    "fields" : [
        {
            "name" : "doi",
            "list" : false,
            "widgetType": "TextField",
            "config": {
                "type" : "str"
            },
            "required" : true
        }
    ]
}

[longshuicy]

Since this right now is also an arbitrary list, could you also make it a dropdown?

"int": int,
"float": float,
"str": str,
"bool": bool,
"date": datetime.date,
"time": datetime.time,
"dict": dict,  # TODO: does this work?
"enum": str,  # TODO: need a way to validate enum,
"tuple": tuple,

[longshuicy]

For both the widget type and data type drop downs, can we use more layman's term? e.g. TextField --> Text Box; Select --> Dropdown, Int --> Integer, Float --> Number
You are welcome to improvise a little bit :D

[arunapa]

I've added human readable names in both drop downs

[arunapa]

Some more improvements I've added in the latest commit:

1. Sanity checks while moving between stepper states (previously sanity was executed prior to invoking the API)

2. Added a new "preview" text box so that the user can know what metadata definition is being sent to the backend
   

3. Clicking on the stepper can move between states now

[arunapa]

Bugs addressed:

1. Preview text should not show entries that have been deleted
2. Duplicate menu button
3. Fix the resize issue for the popup page

Pending bugs/improvements to be addressed in future PRs:
Making the navigation between stepper states more intuitive

[longshuicy]

you have it duplicated here :-P

[arunapa]

I've fixed this issue in the latest commit as well :)

[lmarini]

Looks good. Just a few small improvements we can do on a separate branch and one potential bug.

• We should probably use an example of the context using Dublin Core since it's pretty common
  {"abstract": "http://purl.org/dc/terms/abstract"}
• The first section header is capitalized, but the second is not. We should be consistent, maybe change to "Create metadata definitions"
• Maybe put to the two check boxes on the same line? "Contains list" "Required". What does "Contains list" do?
• Can we make the metadata example being editable? So that they don't have to type everything, the curly brackets, etc?

I created an entry that includes a list but the list doesn't work when I try to create an instance of it. Just one field of type list. This is the definition in Mongo:

{ "_id": { "$oid": "635ff6063230ca72094d85d7" }, "name": "Abstract", "description": "Just another abstract", "context": { "abstract": "http://purl.org/dc/terms/abstract" }, "context_url": null, "fields": [ { "id": { "$oid": "635ff6063230ca72094d85d8" }, "name": "Abstract", "list": false, "widgetType": "Select", "config": { "id": { "$oid": "635ff6063230ca72094d85da" }, "type": "enum" }, "required": false } ], "creator": { "id": { "$oid": "632b39f29b06a45e416a33f4" }, "email": "[email protected]", "first_name": "Luigi", "last_name": "Marini" }}

[arunapa]

I've addressed the following:

1. Making the capitalization consistent
2. Changing the default context example
3. Making the context example editable for the user to modify quickly while submitting the form
4. Checkboxes in same row