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

[Feature] Offer simple, comprehensive "download license statement" link for all formats #503

Open
metasj opened this issue Feb 23, 2024 · 1 comment
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed 🧹 status: ticket work required Needs more details before it can be worked on 💬 talk: discussion Open for discussions and feedback

Comments

@metasj
Copy link

metasj commented Feb 23, 2024

Problem

After filling out the chooser, it's unclear how to save a copy of the results. There is a double modal! with four total tabs, each with a different way to copy or save the result. Make a default "download" link that saves all the versions of the result, perhaps in a little "License-statements" folder.

Description

  1. Plain Text only shows up for Print Work or Media, though some people might want the plain text online.
  2. Plain Text, Rich Text, and HTML offer a "Copy" button and a full / abbreviated option for the license name.
  3. XMP offers to download XMP metadata (I haven't looked inside: does it use abbreviations? :)

A "download all license statements" link could download a zipped folder with one file for each statement format, with some canonical name based on the work and author.

This would be especially useful for someone generating a lot of these who wants to "download all" and then "make a new statement" a number of times in succession.

Implementation

@metasj metasj added ✨ goal: improvement Improvement to an existing feature 💻 aspect: code Concerns the software code in the repository 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work 🟩 priority: low Low priority and doesn't need to be rushed labels Feb 23, 2024
@possumbilities possumbilities added 💬 talk: discussion Open for discussions and feedback 🧹 status: ticket work required Needs more details before it can be worked on and removed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work labels Feb 27, 2024
@possumbilities
Copy link
Contributor

I think this merits a larger conversation around a feature such as this before its moved forward.

@TimidRobot TimidRobot removed the 🧹 status: ticket work required Needs more details before it can be worked on label Jul 9, 2024
@cc-open-source-bot cc-open-source-bot added the 🏷 status: label work required Needs proper labelling before it can be worked on label Jul 9, 2024
@TimidRobot TimidRobot moved this to Triage in WebDev Sep 10, 2024
@possumbilities possumbilities added 🧹 status: ticket work required Needs more details before it can be worked on and removed 🏷 status: label work required Needs proper labelling before it can be worked on labels Sep 18, 2024
@possumbilities possumbilities moved this from Triage to Backlog in WebDev Sep 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed 🧹 status: ticket work required Needs more details before it can be worked on 💬 talk: discussion Open for discussions and feedback
Projects
Status: Backlog
Development

No branches or pull requests

4 participants