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

Update Databases / Add New Databases #45

Open
smahaffey opened this issue Feb 7, 2023 · 9 comments
Open

Update Databases / Add New Databases #45

smahaffey opened this issue Feb 7, 2023 · 9 comments
Assignees

Comments

@smahaffey
Copy link
Collaborator

We will start work on updating:
miRTarBase – v7 -> v9
TargetScan – v7.2 -> v8

Are there any databases you would like to request? Please comment.

@smahaffey smahaffey self-assigned this Feb 7, 2023
@tracywan9
Copy link

Thanks a lot for your upcoming update!

@EvenZhang-spec
Copy link

Thinks,mirWalk?

@chemy-cm
Copy link

Thanks a lot. By the way, Has the database been updated so far?

@knokknok
Copy link

knokknok commented Sep 8, 2023

Would it be possible to have a status update?
🙏

@smahaffey
Copy link
Collaborator Author

The good news is that I can spend some time on it now. I received the green light this week. The bad news is that I haven't started yet. I will post an update with an estimated timeline soon.

@jeremydavisturak
Copy link

Is it possible to download a snapshot of all the data in the database (both before and after the update)?

@smahaffey
Copy link
Collaborator Author

@jeremydavisturak The updated database will be a new complete version so the previous versions will all still be available for the purpose of allowing replication of searches and previous results. Any database version can still be used. The R package provides functionality to select the database version for queries.

As far as downloading the full database, we will have to discuss it. I know at least one of the miRNA-Target databases had a restriction on allowing downloading data from us directly even thought they granted permission to incorporate it into MultiMiR. I'll add it to the list for discussion with the group.

@mattbcvs
Copy link

Thanks for the great tool, providing a lot of avenues for our lab.

Some comments around the entries for "validated" databases:

  • Source_type column entries are unclear to me, why are some interactions "functional" and others "functional(weak)"?
  • Experiment category naming looks a bit inconsistent e.g. "immunoblotting" and "immunoblot analysis", further some are seperated by a "//" and others by ";" which can add confusion.

Would help to make more user-friendly, thanks again for the tool though!

@smahaffey
Copy link
Collaborator Author

@mattbcvs Thank you for the feedback. I'm getting started with the update now. So I'll try to keep these in mind. For these issues they are from the original source. I believe they did have a reason for the functional vs functional(weak) interactions. So we don't want to alter the original meaning assigned to those distinctions as we're summarizing them across sources.

I do feel as though I could look at the separator issue and try to make everything consistent with this update. I will review each database and see what I can do so everything is slightly more consistent without altering the original data provided by these sources.

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

7 participants