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

Synchronise metadata with global site #106

Open
3 tasks
jazzsequence opened this issue Mar 4, 2021 · 5 comments
Open
3 tasks

Synchronise metadata with global site #106

jazzsequence opened this issue Mar 4, 2021 · 5 comments
Labels
blocked This item can't be moved forward at this time, explanation to be found in comments should have Should be done, medium priority for now

Comments

@jazzsequence
Copy link
Contributor

jazzsequence commented Mar 4, 2021

We need to be able to update metadata on a local site. Specific examples include a multi-language site that uses subsites for each language (e.g. to localize alt text, description, tags, etc, on each language site).

Metadata has a full copy on each site. If the user doesn't want to override the metadata, the metadata should be synchronised/inherited from the global site.

Acceptance Criteria:

  • When I use a media file, if I do not override the metadata, it should use the metadata from the global copy
  • When I use a media file, if I override the metadata, it should use the metadata from the local copy
  • When I edit a media file, I should be able to choose whether metadata is overridden local or inherited from the global copy
@rmccue rmccue added the should have Should be done, medium priority for now label Apr 29, 2021
@rmccue rmccue changed the title Update metadata on a per-site basis Synchronise metadata with global site Jun 8, 2021
@rmccue rmccue added this to the v8 sprint 4 milestone Jun 14, 2021
@rmccue
Copy link
Member

rmccue commented Jun 15, 2021

Going to research the need here a little.

@rmccue rmccue removed this from the v8 sprint 4 milestone Jun 22, 2021
@rmccue rmccue added the blocked This item can't be moved forward at this time, explanation to be found in comments label Aug 3, 2021
@shadyvb
Copy link
Contributor

shadyvb commented Aug 19, 2021

Is this still blocked ? If so, can we link the blocking issue for reference.

@rmccue
Copy link
Member

rmccue commented Sep 15, 2021

@shadyvb This was blocked on research rather than an issue, and don't think we had an issue for that aspect. We should though.

@shadyvb
Copy link
Contributor

shadyvb commented Sep 27, 2021

@rmccue can we use this issue for research instead ? is this something I can help with ? or is it about researching how existing clients need this to work ?

@rmccue
Copy link
Member

rmccue commented Sep 27, 2021

It was about researching with our pilot users about how exactly they wanted to use it, but that rollout has been blocked, so we didn't get any feedback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked This item can't be moved forward at this time, explanation to be found in comments should have Should be done, medium priority for now
Projects
None yet
Development

No branches or pull requests

4 participants