Repository navigation
[9.0] feat: add scitag support - #8263
Merged
Merged
Conversation
chaen
reviewed
Sep 4, 2025
fstagni
force-pushed
the
90_scitags
branch
6 times, most recently
from
September 5, 2025 08:28
59137f9 to
da61742
Compare
chaen
reviewed
Sep 5, 2025
fstagni
force-pushed
the
90_scitags
branch
3 times, most recently
from
September 8, 2025 12:17
e5624e5 to
bea1aec
Compare
chaen
reviewed
Oct 9, 2025
chaen
marked this pull request as draft
October 14, 2025 07:50
chaen
force-pushed
the
90_scitags
branch
2 times, most recently
from
November 14, 2025 16:50
b6b032d to
da29113
Compare
fstagni
marked this pull request as ready for review
November 17, 2025 13:40
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Only for FTS transfers (I do not think we want others...?).
BEGINRELEASENOTES
*DMS
NEW: add scitag to FTS transfers
ENDRELEASENOTES
PS: the scitag "API" is https://scitags.org/api.json. The "activityName" as coded should be match the "FTS3 activity", which is of course VO-specific. In LHCb it's coded as simple as:
(pay attention that here it's spelled "Data Challenge" while in the scitag API is "DataChallenge".