cleverdatasets/dataset-uploader

Fork

You've already forked dataset-uploader

Code Issues 23 Pull requests 13 Projects Releases Packages Wiki Activity Actions

Add multiple files to the dataset_config. #36

New issue

Open

opened 2025-12-16 19:24:16 +00:00 by brent.edwards · 0 comments

brent.edwards commented

2025-12-16 19:24:16 +00:00

Member

Copy link

Uniprot is spread among multiple files.

The dataset uploader needs to accept multiple files. (Is it possible for the uploader to discover the files?)

Uniprot is spread among [multiple files](https://ftp.uniprot.org/pub/databases/uniprot/current_release/rdf/). The dataset uploader needs to accept multiple files. (Is it possible for the uploader to discover the files?)

No Branch/Tag specified

master

stream-download-convert-upload-merge-15-refactor-rdf-converters

path-too-long-fix

unified-final

stream-download-convert-upload

integrate/all

merged

shared-parallelism

35-xz-compression

push-to-hub

15-refactor-rdf-converters

27-allow-download-ftp

memory-issue-fix

30-temporary-files

19-rewrite-upload-all-datasets

16-error-messages-and-logging

6-behave-tests

8-devcontainer-setup

7-dockerfile-setup

14-cli-entry-points

mypy-and-pylint

No results found.

Labels

Clear labels

Blocked

A ticket in a blocked state and unable to complete until some other task is completed first.

Bounty

$100

A bounty of $100 for any open-source contributor who provides a MR that solves this issue

Bounty

$1000

A bounty of $1000 for any open-source contributor who provides a MR that solves this issue

Bounty

$10000

A bounty of $10000 for any open-source contributor who provides a MR that solves this issue

Bounty

$20

A bounty of $20 for any open-source contributor who provides a MR that solves this issue

Bounty

$2000

A bounty of $2000 for any open-source contributor who provides a MR that solves this issue

Bounty

$250

A bounty of $250 for any open-source contributor who provides a MR that solves this issue

Bounty

$50

A bounty of $50 for any open-source contributor who provides a MR that solves this issue

Bounty

$500

A bounty of $500 for any open-source contributor who provides a MR that solves this issue

Bounty

$5000

A bounty of $5000 for any open-source contributor who provides a MR that solves this issue

Bounty

$750

A bounty of $750 for any open-source contributor who provides a MR that solves this issue

MoSCoW

Could have

Could have feature in order to satisfy the epic/legendary.

MoSCoW

Must have

Must have feature in order to satisfy the epic/legendary.

MoSCoW

Should have

Should have feature in order to satisfy the epic/legendary.

Needs feedback

There are questions in the ticket that can not be completed until the project owner provides clarity.

Points

1 man-hours worth of work for an expert with no learning curve.

Points

13 man-hours worth of work for an expert with no learning curve.

Points

2 man-hours worth of work for an expert with no learning curve.

Points

21 man-hours worth of work for an expert with no learning curve.

Points

3 man-hours worth of work for an expert with no learning curve.

Points

34 man-hours worth of work for an expert with no learning curve.

Points

5 man-hours worth of work for an expert with no learning curve.

Points

55 man-hours worth of work for an expert with no learning curve.

Points

8 man-hours worth of work for an expert with no learning curve.

Points

88 man-hours worth of work for an expert with no learning curve.

Priority

Backlog

This ticket has backlogged priority and is not to be worked on yet

Priority

Critical

The priority is critical

The priority is medium

Signed-off: Owner

When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

Signed-off: Scrum Master

When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

Signed-off: Tech Lead

When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

Spike

A ticket for learning a tool or technology that is needed to be able to do future planning and design.

State

Completed

The ticket has been fully implemented, completed, and merged with the source code. This label should only be applied once a ticket is closed.

State

Duplicate

A ticket that represents the same content as an existing ticket.

State

In Progress

A ticket that is actively being developed.

State

In Review

A ticket that has had some code completed to implement but is waiting to pass peer review and is not yet merged in.

State

Paused

This ticket's work started but wasn't finished. It's on hold (likely in a feature branch) and will be resumed later, either due to a blocker or a delay.

State

Unverified

All new tickets start in this state. A developer may set it to show the ticket is unverified. This means we haven't agreed to work on it. It will either move to a verified state or be closed as wontdo.

State

Verified

The issue has been verified by a developer as legitimate. It will be worked on and verified tickets are now considered part of the backlog.

State

Wont Do

This ticket has been decided it wont be done. This may mean the bug has been determined to not be real (cant verify) or the feature is one we have decided we dont want to adopt.

Type

Bug

Something that doesnt work as intended.

Type

Discussion

Anytime a ticket represents a discussion about a subject and doesnt fall into one of the other categories.

Type

Documentation

An error or improvement needed in the documentation.

Type

Epic

Any first tier epic. That is, an epic which contains only issues as children and will not have sub-epics.

Type

Feature

Some new functionality not present.

Type

Legendary

A type of Epic which will contain other Epics.

Type

Support

Someone needs help using the project.

Type

Task

A generic task that doesnt fit into the other type categories.

Type

Testing

Work exclusively focusing on fixing or expanding testing.

No labels

Signed-off: Scrum Master

Signed-off: Tech Lead

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

cleverdatasets/dataset-uploader#36

Reference in a new issue

Repository

cleverdatasets/dataset-uploader

Title

Body

No description provided.

Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?

Rows
Columns