Skip to content
GitLab
Projects
Groups
Snippets
/
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
Menu
Open sidebar
nomad-lab
nomad-FAIR
Commits
7b692409
Commit
7b692409
authored
Jan 17, 2020
by
Markus Scheidgen
Browse files
Minor GUI fixes.
parent
b92d5f66
Pipeline
#67211
passed with stages
in 28 minutes and 58 seconds
Changes
6
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
gui/public/index.html
View file @
7b692409
...
...
@@ -8,6 +8,7 @@
</script>
<script
src=
"https://unpkg.com/pace-js@1.0.2/pace.min.js"
></script>
<link
href=
"%PUBLIC_URL%/pace.css"
rel=
"stylesheet"
/>
<link
href=
"%PUBLIC_URL%/main.css"
rel=
"stylesheet"
/>
<meta
charset=
"utf-8"
>
<meta
name=
"viewport"
content=
"width=device-width, initial-scale=1, shrink-to-fit=no"
>
...
...
@@ -35,7 +36,7 @@
<link
rel=
"stylesheet"
href=
"https://fonts.googleapis.com/icon?family=Material+Icons"
>
<title>
NOMAD upload
</title>
</head>
<body
style=
"overflow-y: hidden;"
>
<body>
<noscript>
You need to enable JavaScript to run this app.
</noscript>
...
...
gui/public/main.css
0 → 100644
View file @
7b692409
body
{
overflow-y
:
hidden
;
}
\ No newline at end of file
gui/src/components/About.js
View file @
7b692409
...
...
@@ -90,7 +90,7 @@ class About extends React.Component {
- domain:
${
info
?
info
.
domain
.
name
:
'
loading
'
}
- git:
\`
${
info
?
info
.
git
.
ref
:
'
loading
'
}
;
${
info
?
info
.
git
.
version
:
'
loading
'
}
\`
- last commit message: *
${
info
?
info
.
git
.
log
:
'
loading
'
}
*
- codes:
${
info
?
info
.
codes
.
join
(
'
,
'
)
:
'
loading
'
}
-
supported
codes:
${
info
?
info
.
codes
.
join
(
'
,
'
)
:
'
loading
'
}
- parsers:
${
info
?
info
.
parsers
.
join
(
'
,
'
)
:
'
loading
'
}
- normalizers:
${
info
?
info
.
normalizers
.
join
(
'
,
'
)
:
'
loading
'
}
`
}
<
/Markdown
>
...
...
gui/src/components/api.js
View file @
7b692409
...
...
@@ -586,6 +586,9 @@ export class ApiProviderComponent extends React.Component {
api
.
getInfo
()
.
catch
(
handleApiError
)
.
then
(
info
=>
{
if
(
info
.
parsers
)
{
info
.
parsers
.
sort
()
}
this
.
setState
({
info
:
info
})
})
.
catch
(
error
=>
{
...
...
gui/src/components/search/SearchPage.js
View file @
7b692409
...
...
@@ -10,7 +10,7 @@ import qs from 'qs'
export
const
help
=
`
This page allows you to **search** in NOMAD's data. The upper part of this page
gives you various options to enter and configure your search. The lower
half
gives you various options to enter and configure your search. The lower
part
shows all data that fulfills your search criteria.
NOMAD's *domain-aware* search allows you to screen data by filtering based on
...
...
@@ -26,13 +26,13 @@ NOMAD's data as a periodic table or metadata charts. You can click the various
visualization elements to filter for respective quantities.
The visual representations show metrics for all data that fit your criteria.
You can display *entries* (
e.g
. code runs), *unique entries*, and *datasets*.
You can display *entries* (
i.e
. code runs), *unique entries*, and *datasets*.
Other more specific metrics might be available.
The results tabs gives you a quick overview of all entries and datasets that fit your search.
You can click entries to see more details, download data, see the archive, etc. The *entries*
tab displays individual entries (
e.g
. code runs), the *grouped entries* tab will group
entries with similar metadata (
e.g.
it will group entries for the same material from the
tab displays individual entries (
i.e
. code runs), the *grouped entries* tab will group
entries with similar metadata (it will group entries for the same material from the
same user). The *dataset* tab, shows entry curated by user created datasets. You can
click on datasets for a search page that will only display entries from the respective
dataset.
...
...
@@ -42,7 +42,7 @@ entries (or all entries) can be downloaded. The download will contain all user p
raw calculation input and output files.
You can click entries to see more details about them. The details button will navigate
you to an entr
ie
s page. Th
ese
entry page
s
will show more metadata, raw files, the
you to an entr
y'
s page. Th
is
entry page will show more metadata, raw files, the
entry's archive, and processing logs.
`
...
...
gui/src/components/uploads/Uploads.js
View file @
7b692409
...
...
@@ -36,10 +36,10 @@ output files, as well as any other auxiliary files that you might have created.
You can put data from multiple calculations into one file using as many directories as
you like. NOMAD will consider all files on a single directory to form a single entry.
Ideally, you put only files related to a single code run into each directory. If users
want to download an entry, they
will
download all files in the respective directory.
want to download an entry, they
can
download all files in the respective directory.
The directory structure can be nested.
Drop your archive file(s)
below
. You can also click the dropbox to select the file from
Drop your archive file(s)
on the dropbox
. You can also click the dropbox to select the file from
your hard drive. Alternatively, you can upload files via the given shell command.
Replace
\`
<local_file>
\`
with your archive file. After executing the command,
return here and press the reload button below).
...
...
@@ -66,16 +66,16 @@ If you press publish, a dialog will appear that allows you to set an
data with selected users, create a DOI for your data, and later publish the data.
The *embargo* might last up to 36 month before data becomes public automatically.
During an *embargo* the data (and datasets created from this data) are only visible to you
and users you *share with*
t
he
data
.
and users you
share the data with (i.e. users you added under
*share with*
w
he
n editing entries)
.
#### Processing errors
We distinguish between uploads that fail processing completely and uploads that contain
entries that could not be processed. The former might be caused by issues during the
upload, bad file formats, etc. The latter (f
o
r more common) case means that not all of the provided
upload, bad file formats, etc. The latter (f
a
r more common) case means that not all of the provided
code output files could be parsed by our parsers. The processing logs of the failed entries might provide some insight.
You can
not publish uploads that failed processing completely. Frankly, in most
You cannot publish uploads that failed processing completely. Frankly, in most
cases there won't be any data to publish anyways. In the case of failed processing of
some entries however, the data can still be published. You will be able to share it and create
DOIs for it, etc. The only shortcomings will be missing metadata (labeled *not processed*
...
...
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment