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

Improve Data UI #634

Open
3 of 6 tasks
michamos opened this issue Dec 12, 2024 · 3 comments
Open
3 of 6 tasks

Improve Data UI #634

michamos opened this issue Dec 12, 2024 · 3 comments
Assignees
Milestone

Comments

@michamos
Copy link
Collaborator

michamos commented Dec 12, 2024

The Data UI has several shortcomings:

@drjova
Copy link
Contributor

drjova commented Dec 13, 2024

@michamos should the link to literature be both in search and detail? And just to verify, we are talking about literature.record.$ref right?

@drjova
Copy link
Contributor

drjova commented Dec 13, 2024

and also what I should display in the dropdown? The control_number? for example

        "literature": [
            {
                "record": {
                    "$ref": "http://localhost:5000/api/literature/1234"
                },
                "record": {
                    "$ref": "http://localhost:5000/api/literature/5678"
                }
            }
        ]

@michamos
Copy link
Collaborator Author

Link as button in search, text in detailed view. Yes, that's the correct field. For the detailed view, you can reuse what we do for seminars: https://inspirehep.net/seminars/2853636. For the dropdown you can also use the title if there is more than one (but there won't be for HEPData, so not an issue currently).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants