sshoc-marketplace-frontend issueshttps://gitlab.gwdg.de/sshoc/sshoc-marketplace-frontend/-/issues2019-12-05T12:31:22Zhttps://gitlab.gwdg.de/sshoc/sshoc-marketplace-frontend/-/issues/2Basic detail view client-side2019-12-05T12:31:22ZMatej DurcoBasic detail view client-sideImplement a generic minimal detail view for items, comprising Title and a key-value table of properties.
No special requirements on design, but it needs to exhibit the functionality of being able to jump to related items. (e.g. Tool -> ...Implement a generic minimal detail view for items, comprising Title and a key-value table of properties.
No special requirements on design, but it needs to exhibit the functionality of being able to jump to related items. (e.g. Tool -> Tutorial)
Using the corresponding API-endpoint (for development no need to wait for the actual API-implementation sshoc-marketplace-backend#1, can rely on serving sample data from mock/test server)
Minimal viable productStefan ProbstStefan Probst2019-10-17https://gitlab.gwdg.de/sshoc/sshoc-marketplace-frontend/-/issues/1Basic search client side2019-12-04T19:41:04ZMatej DurcoBasic search client sideA minimal view with
* search bar
* rendering of the result set
* at least activity-type facet
Using the corresponding API-endpoint (serving sample data from mock/test server, independent of the server implementation)
Should show-cas...A minimal view with
* search bar
* rendering of the result set
* at least activity-type facet
Using the corresponding API-endpoint (serving sample data from mock/test server, independent of the server implementation)
Should show-case combination of full-text search with facet-filtering
No special requirements on the design, this will be applied once available.Minimal viable productStefan ProbstStefan Probsthttps://gitlab.gwdg.de/sshoc/sshoc-marketplace-frontend/-/issues/38update MP logo - from alpha to beta2020-12-10T14:49:30ZLaure Barbotupdate MP logo - from alpha to betalogo of the MP should be updated and indicate beta instead of alpha
![image](/uploads/a9c4cb88cd30a0755f91ff9211cdcbd2/image.png)logo of the MP should be updated and indicate beta instead of alpha
![image](/uploads/a9c4cb88cd30a0755f91ff9211cdcbd2/image.png)Design review 2020-10Justyna WytrazekJustyna Wytrazekhttps://gitlab.gwdg.de/sshoc/sshoc-marketplace-frontend/-/issues/35Re-think the start page2020-12-23T12:06:18ZKlaus IllmayerRe-think the start pageFeedback of reviewers showed, that the start page needs to be re-thought, e.g. to make the start page more lively.
Especially the "last added" was not seen as very useful. Instead there were ideas to show "Recommended" or an "Editors' p...Feedback of reviewers showed, that the start page needs to be re-thought, e.g. to make the start page more lively.
Especially the "last added" was not seen as very useful. Instead there were ideas to show "Recommended" or an "Editors' picks" section.
Also there was some critic on the browse function. One idea by @matej.durco is to show instead the first five items of selected facets prominent on the start page (maybe directly below the search bar and move the background image somewhere else).
There was also a remark that the background image should show more diversity and that the landmarks are too stereotypical. Additionally, the description labels ("Researchers in political science") seems to be unnecessary.
Looks like a more general issue, how we can rearrange the information on the start page. This may also include information on curation or information for the community.
@wytrazek @lbarbot @matej.durco @stefan.probst @frank.fischer01 @clara.petitfils - if you have ideas and comments, please add them here, also please add further debaters.Design review 2020-10https://gitlab.gwdg.de/sshoc/sshoc-marketplace-frontend/-/issues/34Have a grid view for the search results2021-03-17T13:34:01ZKlaus IllmayerHave a grid view for the search resultsThere was the idea of a reviewer to have the option to show the search results in a grid (e.g. 3 x 3 items), allowing to switch between list and grid view.
@wytrazek @stefan.probst - what do you think about this idea?There was the idea of a reviewer to have the option to show the search results in a grid (e.g. 3 x 3 items), allowing to switch between list and grid view.
@wytrazek @stefan.probst - what do you think about this idea?Design review 2020-10https://gitlab.gwdg.de/sshoc/sshoc-marketplace-frontend/-/issues/33Fixed menu bar during scrolling2021-03-17T13:29:56ZKlaus IllmayerFixed menu bar during scrollingOne reviewer asked for a fixed menu bar during scrolling on the website.
@wytrazek @stefan.probst - what are your opinions on this?One reviewer asked for a fixed menu bar during scrolling on the website.
@wytrazek @stefan.probst - what are your opinions on this?Design review 2020-10https://gitlab.gwdg.de/sshoc/sshoc-marketplace-frontend/-/issues/32Rethink icons for items2020-12-23T09:19:06ZKlaus IllmayerRethink icons for itemsReviewers claimed that the icons for the items in the search results are "too similar and too detailed".
Currently, there is also a change from "solutions" to "workflows", so that the "S" in the icon of workflows doesn't fit anymore.
In ...Reviewers claimed that the icons for the items in the search results are "too similar and too detailed".
Currently, there is also a change from "solutions" to "workflows", so that the "S" in the icon of workflows doesn't fit anymore.
In general, there was the discussion if having only a letter and a different color for distinction gives a good indicator for browsing the different types of items we have (additionally the window style of the icons was not so well appreciated). Also, there will be a new type available ("Publications") and one type will change the name (from "Tools" to "Tools & services".
@wytrazek - What is your opinion on new icons for the different item types? Do you have some ideas on this?
See also discussion in #12Design review 2020-10https://gitlab.gwdg.de/sshoc/sshoc-marketplace-frontend/-/issues/31Fonts too small2021-03-17T13:30:34ZKlaus IllmayerFonts too smallNearly all reviewers commented on too small fonts for the MP.
@wytrazek - what is your opinion on the too small fonts?
There was also a remark that "Fonts (Ubuntu and Open Sans) are too similar to be a pair on one website" (I know that...Nearly all reviewers commented on too small fonts for the MP.
@wytrazek - what is your opinion on the too small fonts?
There was also a remark that "Fonts (Ubuntu and Open Sans) are too similar to be a pair on one website" (I know that this conflicts with the SSHOC brand guidelines, maybe we report this back, what do you think @lbarbot ?).Design review 2020-10https://gitlab.gwdg.de/sshoc/sshoc-marketplace-frontend/-/issues/23Some observations on frontend on base of my ingest experiment2021-03-17T13:57:02ZKlaus IllmayerSome observations on frontend on base of my ingest experimentGeneral
* ~~Instead of "activities" we now use "workflows" (does include lables as well as API endpoints)~~
* ~~Instead of property "cover-image" we now use "media"~~
* ~~Show images of the properties "thumbnail" and "media" (we don't ho...General
* ~~Instead of "activities" we now use "workflows" (does include lables as well as API endpoints)~~
* ~~Instead of property "cover-image" we now use "media"~~
* ~~Show images of the properties "thumbnail" and "media" (we don't host them, so there are references to 3rd party websites that may deliver 404 or may took quite some time to deliver the image): use thumbnail instead of the icon (but we can't control this thumbnails: maybe this is a big png-file, so there is some dange in using this thumbnail instead of the default icon of an item: needs to be discussed)~~
* Keywords (also activities) in detail view should be clickable (after click, show all items with with this keyword/activity > via facet? currently it is not searchable, maybe that is good, not sure about it) [unclear about what the interaction should fire: really show all items to a keyword, that can be a lot of them]
Not shown in detail view of an item:
* Field "licenses" (mulitple values) e.g. https://sshoc-marketplace.acdh-dev.oeaw.ac.at/tools/1 / https://sshoc-marketplace-api.acdh-dev.oeaw.ac.at/api/tools/1 (manual ingested tool "Gephi"): it differs to property "license-type" but has an implicit connection (group them together? but usually it should be either licenses or license-type and not both mixed)
* (tbd if necessary in detail view) Field "informationContributors" (multiple values) e.g. https://sshoc-marketplace.acdh-dev.oeaw.ac.at/tools/1
* ~~Field "repository" e.g. https://sshoc-marketplace.acdh-dev.oeaw.ac.at/tools/1 (not sure, if we kick this field out- need to be discussed)~~
* (problem of backend, create issue there; tbd what should be delivered, see #5) Box "Related": The items in this box are different shown than in the search results, e.g. no activity shown and contributors are currently empty, also not property "object-type" is used instead field "type" (e.g. https://sshoc-marketplace.acdh-dev.oeaw.ac.at/tools/1 - item "Introduction to GEPHI" should be "Tutorial" instead of "Training material")
Missing facets
* Field "licenses" (but maybe also property license-type): license does have a more generic type like "free" or "open-source" (licenses[].types[]) that maybe more suitable for the facet, see: https://sshoc-marketplace-api.acdh-dev.oeaw.ac.at/api/license-types ; this generic type is also bound to the property "license-type"
* ~~Facet of field "sources" misses a title~~
Behaviour
* ~~Searching for e.g. "user story b" and clicking into an item deletes the search value. Expected that the search string still stays in the search box.~~
* [scroll to top when toggling facets] Scrolling down in search result (all items) so that the header is not visible anymore: clicking now on an activity that only has a small amount like "Sharing (1)". Expected that it jumps to the start of the page, so that this item is shown, instead it stays in the middle of the page.Design review 2020-10Stefan ProbstStefan Probsthttps://gitlab.gwdg.de/sshoc/sshoc-marketplace-frontend/-/issues/40Promote recommended items to frontpage2021-01-05T16:16:53ZMatej DurcoPromote recommended items to frontpageAs proposed in the design and requested by users, we want recommended items promoted to website.
Initially at least, this is a static list of a few items that we as team select, as discussed in [basecamp](https://3.basecamp.com/4165192/...As proposed in the design and requested by users, we want recommended items promoted to website.
Initially at least, this is a static list of a few items that we as team select, as discussed in [basecamp](https://3.basecamp.com/4165192/buckets/10902638/todos/3247884396#__recording_3276065991)
They will be marked with `keyword=recommended`
And can be displayed on the frontpage via a simple query filtering on that keyword.
(notify: @klaus.illmayer, @lbarbot, @frank.fischer01, @stefan.probst)Beta release (M24)Stefan ProbstStefan Probsthttps://gitlab.gwdg.de/sshoc/sshoc-marketplace-frontend/-/issues/39Not all information available appears in the detail view2020-12-29T11:14:43ZMatej DurcoNot all information available appears in the detail viewSome attributes (and properties?) seem not to appear in the detail view even though they are available in the data.
**Contributors in Publications**, example :
https://sshoc-marketplace.acdh-dev.oeaw.ac.at/publication/3664
vs.
https://s...Some attributes (and properties?) seem not to appear in the detail view even though they are available in the data.
**Contributors in Publications**, example :
https://sshoc-marketplace.acdh-dev.oeaw.ac.at/publication/3664
vs.
https://sshoc-marketplace-api.acdh-dev.oeaw.ac.at/api/publications/3664
@lbarbot do you have examples of dynamic properties that don't appear? I can't find any at the moment.
(notify: @klaus.illmayer)Beta release (M24)Stefan ProbstStefan Probsthttps://gitlab.gwdg.de/sshoc/sshoc-marketplace-frontend/-/issues/28Mechanism to update content of static pages2022-07-28T14:43:12ZMatej DurcoMechanism to update content of static pagesSince we have no CMS, content is directly part of the code.
Should be made updateable by moderators.
We propose:
* Imprint: fetch template from https://shared.acdh.oeaw.ac.at/acdh-common-assets/api/data/ and inject specific content from...Since we have no CMS, content is directly part of the code.
Should be made updateable by moderators.
We propose:
* Imprint: fetch template from https://shared.acdh.oeaw.ac.at/acdh-common-assets/api/data/ and inject specific content from some config-file from sshoc-mp-frontend-repo
* everything else About, Contact, etc.: config-files (md, yaml, whatever) in sshoc-mp-frontend-repoBeta release (M24)Stefan ProbstStefan Probsthttps://gitlab.gwdg.de/sshoc/sshoc-marketplace-frontend/-/issues/15Handle entities without accessibleAt2020-09-16T14:22:25ZKlaus IllmayerHandle entities without accessibleAtIt is possible that an entity does not have an accessibleAt-URL, see e.g. this [tool](https://sshoc-marketplace.acdh-dev.oeaw.ac.at/tools/1244). Currently the button "Go to tool" shows up that is not clickable. That is not a good soultio...It is possible that an entity does not have an accessibleAt-URL, see e.g. this [tool](https://sshoc-marketplace.acdh-dev.oeaw.ac.at/tools/1244). Currently the button "Go to tool" shows up that is not clickable. That is not a good soultion: Either don't show the button or have a different text (are there other options?).
Side note: in this case the URL to the tool is mentioned only in the description. Curation needs to identify items without accessibleAt-URL (something to show up on the curation workflow: x entities without accessibleAt) and try to find out the URL.Beta release (M24)Stefan ProbstStefan Probsthttps://gitlab.gwdg.de/sshoc/sshoc-marketplace-frontend/-/issues/14Implement autocomplete in search2020-12-23T09:18:20ZMatej DurcoImplement autocomplete in searchWe need to define the source of autocompleteWe need to define the source of autocompleteBeta release (M24)Stefan ProbstStefan Probst2020-08-27https://gitlab.gwdg.de/sshoc/sshoc-marketplace-frontend/-/issues/12Show a thumbnail2020-12-23T09:16:30ZMatej DurcoShow a thumbnailwe have `thumbnail` attribute already.
Let's render it as image in the detail view.
Still needs to be decided, where to position it.we have `thumbnail` attribute already.
Let's render it as image in the detail view.
Still needs to be decided, where to position it.Beta release (M24)Stefan ProbstStefan Probsthttps://gitlab.gwdg.de/sshoc/sshoc-marketplace-frontend/-/issues/10Update texts (intro, about, etc.)2021-03-17T13:31:25ZTomasz ParkoลaUpdate texts (intro, about, etc.)- replace placeholder of "entry sentence" on the main site (the one above search box)
- update "about section" with real information (remove subsections that will be empty for the time being)- replace placeholder of "entry sentence" on the main site (the one above search box)
- update "about section" with real information (remove subsections that will be empty for the time being)Beta release (M24)Laure BarbotLaure Barbothttps://gitlab.gwdg.de/sshoc/sshoc-marketplace-frontend/-/issues/44Displaying items related to steps2021-03-22T15:08:43ZMatej DurcoDisplaying items related to stepsWhen an item is related to a step of a workflow, there is a problem displaying its detail view, because steps do not have a dedicated item-representation.
Example of such an item is:
[D4Science.org Gateway - Explore Virtual Research Envi...When an item is related to a step of a workflow, there is a problem displaying its detail view, because steps do not have a dedicated item-representation.
Example of such an item is:
[D4Science.org Gateway - Explore Virtual Research Environments](https://marketplace.sshopencloud.eu/tool-or-service/Oo3zrP)
linked to step 4 "Select Datasets" of the workflow:
[Aggregate different datasets using RUBRICA](https://marketplace.sshopencloud.eu/workflow/FoBJYJ)
This lead to an error `Unreachable: step` and has been hot fixed for the beta-release by not displaying related items for items related to steps (Correct, @stefan.probst?)
We need a more satisfying solution to this.
Suggestion:
create a list-item view for steps that includes the title of and pointer to the parent workflow and can be used in related items lists.
Opinions, other options?
@swolarz, @klaus.illmayer, @mkozak, @stefan.probst, @lbarbotWorkflows implementedStefan ProbstStefan Probsthttps://gitlab.gwdg.de/sshoc/sshoc-marketplace-frontend/-/issues/61edit forms, data model & editorial guidelines2021-05-04T15:16:20ZLaure Barbotedit forms, data model & editorial guidelinesa few comments based on the work going on in T7.4 for the [editorial guidelines](https://docs.google.com/document/d/12VmhR9W4mN7AaOlrZGG2YxCCCsZDbHkuoXjfqfDG4PA/edit#) of the Marketplace, that should be added as documentation/static page...a few comments based on the work going on in T7.4 for the [editorial guidelines](https://docs.google.com/document/d/12VmhR9W4mN7AaOlrZGG2YxCCCsZDbHkuoXjfqfDG4PA/edit#) of the Marketplace, that should be added as documentation/static pages for the beta+ version, and also based on my first tests using the edit forms:
1. we are still looking for the best way to structure the guidelines to support contributors and moderators in the creation and review/approbation of the items. One important idea is the need to prioritise attributes/properties depending on the type of items created (i.e. bibliographic metadata are important if you create a publication, maybe less if you create a tool&service), so we came up with this idea of having **recommended fields** depending on the type of items. This is not part of the data model, but it is probably important to have this reflected in the edit forms, especially for the property section.
2. one other example is the need to adapt the 'step' part of the workflows forms, because even if a step could theoretically supports the same metadata than any other object/entity, only 'label', 'description' and 'related items' are actually displayed on the item view. Based on the discussions we had during T7.4 telcos, we feel a need to also have 'see also' displayed for a step - and maybe even 'media'
3. can we isolate the 'thumbnail' property from the other one in the edit forms? This property doesn't belong to any group ans is displayed in a very different way than the others.
4. we need some clarification regarding the properties recording time (cf.[ #78](https://gitlab.gwdg.de/sshoc/sshoc-marketplace/-/issues/78))
5. as 'description' allows markdown, we can add links, which is somehow redundant with the purpose of 'see also'. Is it a problem?
notify @edward.gray @nicolas.larrousse @frank.fischer01 @wytrazek @matej.durco @klaus.illmayer @stefan.probstBeta+https://gitlab.gwdg.de/sshoc/sshoc-marketplace-frontend/-/issues/37Design the details information2021-11-28T16:46:51ZKlaus IllmayerDesign the details informationCurrently the details information of items is not very well designed. The labels are not highlighted very well and it looks very unstructured. I would expect more structure for these important information and an easily distinction of the...Currently the details information of items is not very well designed. The labels are not highlighted very well and it looks very unstructured. I would expect more structure for these important information and an easily distinction of the different detail informations. Something like intend blocks or use space between the different information parts or a table structure or applying other design ideas would be very welcome, e.g. something like:
```
**Details**
_Activities_ (i)
Analysis
Capture
_Keywords_ (i)
Content Analysis
Modeling
_License type_ (i)
Free
...
```
The (i) could be a tooltip/hover element where a small description of the block is shown (e.g. "Activities use the TADiRAH vocabulary. It describes the research data life cycle where an item can be applied. ...")
This is an open discussion thread. There is currently no pattern given for the detail informations, so it can be seen as a place for creative ideas.
What do you think? @wytrazek @stefan.probst @lbarbot @matej.durco @frank.fischer01Beta+Justyna WytrazekJustyna Wytrazekhttps://gitlab.gwdg.de/sshoc/sshoc-marketplace-frontend/-/issues/97failed to re-save or submit a draft2022-03-25T09:26:38ZLaure Barbotfailed to re-save or submit a draft# ๐ Bug Report
While doing a few tests on stage, I'm working as contributor and have tried to create an item. I saved it as draft. Then, I come back to edit the draft, and when I try to either save again the draft OR to submit the item....# ๐ Bug Report
While doing a few tests on stage, I'm working as contributor and have tried to create an item. I saved it as draft. Then, I come back to edit the draft, and when I try to either save again the draft OR to submit the item. I got the "failed to submit" banner.
## ๐ค Expected Behavior
When coming back on a draft, a contributor should be able to edit it and either to save it as draft again or to submit the item.
## ๐ฏ Current Behavior
It doesn't seem possible to save a draft a 2nd time Or to submit a draft
notify also @edward.gray @matej.durco
---Curation module implementedKlaus IllmayerStefan ProbstKlaus Illmayer