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

Add Magic Card Market set names for each set #78

Closed
KingSupernova31 opened this issue Oct 16, 2018 · 9 comments
Closed

Add Magic Card Market set names for each set #78

KingSupernova31 opened this issue Oct 16, 2018 · 9 comments
Labels
Enhancement New feature or request Help Wanted Extra attention is needed More Information Needed Further information is requested No Fix This will not be worked on

Comments

@KingSupernova31
Copy link

Adding the set name used by https://www.magiccardmarket.eu/Expansions would allow those that use the MTGJSON data to more easily integrate into the pricing data provided by that site.

#67

@ZeldaZach
Copy link
Member

I recently got access to TCGPlayer API and pricing system, so I'd consider that before MKM. We're also not really a pricing system, so I'm not sure if I want to go forward with this.

@ZeldaZach ZeldaZach added More Information Needed Further information is requested No Fix This will not be worked on labels Oct 16, 2018
@fenhl
Copy link
Contributor

fenhl commented Oct 17, 2018

If we're going to implement TCGPlayer IDs, we should also implement MKM IDs. MKM is the only reliable source of Euro prices since the secondary market often looks very different over here.

@ZeldaZach
Copy link
Member

Fair enough, I'll look into it at some point in the future. This is a lower priority for me at the moment

@ZeldaZach ZeldaZach added Enhancement New feature or request Help Wanted Extra attention is needed and removed No Fix This will not be worked on labels Oct 17, 2018
@ZeldaZach ZeldaZach added this to the v4.2 milestone Oct 29, 2018
@ancestral
Copy link

I feel like we should not be including this sort of thing.

Personally I feel like being pure to the data has value. Given we get the data from Scryfall, and argument can be made to keep some of those data points. Otherwise, it ends up being more steps to keep up-to-date with other services that may come and go.

@ZeldaZach
Copy link
Member

@ancestral We're talking about major components to the community, not minor one man shows (except mtgjson of course haha...). Including MKM/TCG Seems logical to me as they are broad seller markets. Including specific stores I would prob be against

Scryfall provides purchase URLs for tcgplayer/MKM, so it would be a simple parse. It would be up to SF to keep such data up to date from what it looks like. This seems doable

@ancestral
Copy link

What’s going to happen is you’re going to get requests for CardKingdom, for MTGGoldfish, for ChannelFireball, coolstuff, PucaTrade… where do you end this?

@nhrsn
Copy link

nhrsn commented Dec 7, 2018

All other services should be bending to the will using the IDs provided by mtgjson. I think adding the IDs used by external sites just encourages more inconsistency across all the MTG services out there.

@ZeldaZach
Copy link
Member

I felt that adding TCGPlayer's id system was appropriate because they have a catered to API network, and we're giving help to those who might want to list and not have to do some grunt work.

If other services provide similar things I'd be willing to consider it, but otherwise I have no further intentions to add additional ID key sets

@ZeldaZach ZeldaZach removed this from the v4.2 milestone Dec 8, 2018
@ZeldaZach ZeldaZach added the No Fix This will not be worked on label Dec 8, 2018
@tooomm
Copy link
Contributor

tooomm commented Dec 8, 2018

MKM has an api as well: https://www.mkmapi.eu/ws/documentation
I didn't look into details...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement New feature or request Help Wanted Extra attention is needed More Information Needed Further information is requested No Fix This will not be worked on
Projects
None yet
Development

No branches or pull requests

6 participants